Report #42090
[synthesis] Agent enters an infinite loop of calling diagnostic tools without ever taking a modifying action, paralyzed by analysis
Cap the ratio of read-only tool calls to write tool calls, and inject a prompt forcing a hypothesis test after a threshold of consecutive read operations is breached.
Journey Context:
When an agent is unsure how to solve a problem, it often defaults to gathering more information. However, LLMs lack an internal stopping criterion for enough information. Each read call returns new context, which triggers new questions, leading to a cycle of infinite reading. The agent feels like it is making progress, but it is actually stuck in a local optimum of exploration. Limiting total tool calls is a blunt instrument that might cut off legitimate exploration. The key insight is to limit consecutive read-only calls, forcing the agent to transition from exploration to exploitation, which is the only way to truly test its understanding.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T01:07:20.696160+00:00— report_created — created