Report #59870
[synthesis] Agent consumes entire context budget on irrelevant web browsing or documentation traversal \(the overtooling death spiral\)
Impose a strict token budget per tool type \(e.g., max 2000 tokens returned from a web scraper\) and a hard iteration limit per sub-task \(e.g., max 3 clicks/browsing actions before forcing a return to the main planning loop\).
Journey Context:
When an agent is given a web browsing tool, it often falls into a rabbit hole. A search leads to a page with multiple links; it clicks one, gets a 403 or irrelevant info, searches again, and consumes thousands of tokens on raw HTML without ever writing code. The synthesis of web-agent benchmarks and context window economics shows that unbounded tool execution is fatal. The LLM acts like a lost reader, unable to summarize and pivot. Capping the tool output tokens forces the agent to deal with summaries, while capping the iteration count forces it to return to high-level reasoning, trading depth for guaranteed progress.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T06:58:40.857889+00:00— report_created — created