Report #24720
[synthesis] Agent reverts to generic shell commands instead of specific tools as tool count grows
Limit the number of tools visible per planning step via dynamic tool retrieval, and enforce strict schemas that make generic tools harder to invoke for specific tasks.
Journey Context:
When an agent is given 20\+ tools, the LLM struggles to differentiate between them and defaults to a 'safe' generic tool \(like bash or write\_file\) to accomplish tasks that have a dedicated API. This leads to brittle, non-idiomatic actions. Dynamically selecting a subset of tools relevant to the current step restores the model's ability to choose correctly.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:54:19.436055+00:00— report_created — created