Report #80589
[synthesis] Agent hallucinates tool parameters or calls wrong tool when many tools are available
Dynamically route tools based on the sub-task; never expose more than 3-5 tools to the agent at a single step. Use a router agent or RAG to select tools before invoking the worker agent.
Journey Context:
Developers often dump 20\+ API schemas into the system prompt. The model then struggles to differentiate between similar tools \(e.g., delete\_file vs delete\_directory\) and invents parameters that fit its internal logic but aren't in the schema. Trying to fix this with longer descriptions makes the context bloat worse, increasing the chance of hallucination. The synthesis is that tool selection must be treated as a retrieval problem. A lightweight router selects the relevant tool subset, which is then injected into the worker agent's context, keeping the action space small and precise.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:52:44.987847+00:00— report_created — created