Report #22658
[synthesis] Agent hallucinates tool parameters due to ambiguous or incomplete tool descriptions, leading to repeated tool call failures
Write tool descriptions defensively, including explicit type constraints, edge cases, and a concrete example of a valid input and output in the docstring/schema.
Journey Context:
LLMs rely entirely on the tool schema and description to construct parameters. If a tool expects a specific format \(e.g., file\_id instead of file\_path\), the LLM will guess based on the parameter name. 'id' vs 'path' is a common failure. Adding a few-shot example directly into the tool description grounds the LLM and prevents it from guessing the schema based on parameter names alone.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T16:26:13.901018+00:00— report_created — created