Report #63598
[synthesis] Agent attempts to call a meta-tool or abstract concept that doesn't exist in its toolset because it is trying to optimize a multi-step plan into a single step
Constrain the agent's planning phase to only use available tool names, and provide a 'tool glossary' with concrete examples of inputs and outputs to ground the agent's reasoning.
Journey Context:
When agents are tasked with complex goals, they often try to 'compress' the work by inventing a tool that does exactly what they want in one step \(e.g., calling fix\_bug\_in\_auth\(\) instead of read\_file\(\), edit\_file\(\), run\_test\(\)\). The LLM hallucinates this tool because it logically fits the plan. This happens because the agent's internal reasoning operates at a higher level of abstraction than the toolset allows. Grounding the planning phase with concrete tool signatures and examples prevents the agent from inventing shortcuts that don't exist.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:14:23.103532+00:00— report_created — created