AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 19, 2026, 10:00 JST

Vercel cuts agent tools 17 to 2; ETH Zurich finds AGENTS.md adds cost

Vercel cuts agent tools 17 to 2; ETH Zurich finds AGENTS.md adds cost

3 Key Points

  1. What happened

    Vercel cut an analytics agent's tools from 17 to 2 (bash and SQL) in December 2025; across 5 questions, successes rose from 4 to 5, time fell from 274.8 to 77.4 seconds, and tokens dropped about 37%. Separately, ETH Zurich found AGENTS.md-style context files generally did not raise task success and raised inference cost over 20% on average.

  2. Why it matters

    The pattern suggests piling on instructions, context files and tools can dilute the important rules and slow the model down, so teams may get better results by trimming instructions while keeping mandatory checks such as hooks and tests.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The discussion started from a claim that overloading the harness makes models underperform, which prompted the author to reconsider the many rules and skills added to their own setup. The reports cited point in a consistent direction: Vercel's reduction of an analytics agent's tools from 17 to 2 coincided with more successes, less time and fewer tokens on its 5-question test, and ETH Zurich's study found that handing over context files such as AGENTS.md did not generally lift task success while raising inference cost by over 20% on average. A Japanese talk by Gota at Harness Engineering Meetup Tokyo #1 in April 2026 described settings files exceeding 300 lines, where changing one task template required edits in 10 places and a full test run took an hour, making it hard to tell which fix mattered.

The author's explanation is that an AI reads everything it is given and tries to obey all of it, so unrelated rules dilute the important ones, similar tools cause hesitation, and small contradictions between rules cause stalls or detours. A concrete example is a rule requiring tests after code changes colliding with a later rule forbidding DB connections, which can lead the agent to skip tests or rewrite them. The proposed split is between instructions, which the AI may or may not follow, and enforcement mechanisms like hooks, permissions, tests and lint, which act regardless of the AI's judgment; overloading problems come mostly from instructions, while enforcement does not confuse the model. In the author's repository, CLAUDE.md went from 102 lines to 50, with rules moved to .claude/rules/ and media-specific information placed in folder-level CLAUDE.md files and skills, and the author says they will write later about how that worked out.

FAQ
How much did Vercel's agent improve after cutting tools?
Across 5 questions, successes went from 4 to 5, time fell from 274.8 seconds to 77.4 seconds, and tokens dropped about 37%.
Did ETH Zurich find that context files like AGENTS.md help?
It found task success rates generally did not improve, while inference cost rose over 20% on average, for both human-written and LLM-generated files.
What is the difference between instructions and enforcement?
Instructions are things written in CLAUDE.md or rules for the AI to follow at its discretion; enforcement is mechanisms like hooks, permissions, tests and lint that stop or check the AI regardless of its judgment.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleLessWrong essay questions AI safety's overhang arguments