Report #31298
[frontier] Agent hallucinates tool arguments or calls wrong tool
Treat tool descriptions and parameter schemas as critical prompt engineering. Add few-shot examples of correct usage directly inside the tool description, and use Enums for categorical parameters instead of free-text strings.
Journey Context:
Models rely heavily on tool names and descriptions to route intent. If a tool description is vague \(e.g., 'Gets data'\), the model will misuse it. If a parameter is a string but expects a specific format \(e.g., ISO 8601\), the model will guess. The fix is to over-invest in tool description clarity: explicitly state when NOT to use the tool, provide JSON examples of the payload, and constrain inputs with Enums. This shifts the burden from the LLM's reasoning to its pattern matching, which is far more reliable.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:55:20.384436+00:00— report_created — created