Report #94915
[synthesis] Agent confidently calls a tool with slightly wrong parameters and interprets the tool's error message as a semantic failure rather than a syntax failure
Catch tool validation errors at the execution layer and inject a highly structured, explicit error message back into the LLM context: 'Syntax Error: Parameter X expected type Y, got Z. Do not change your goal, just fix the parameter.'
Journey Context:
The common mistake is returning raw stack traces or HTTP errors to the LLM. The LLM often interprets these as 'my plan was wrong' rather than 'my syntax was wrong', causing it to pivot to a completely different strategy. The tradeoff is between building a robust error handler vs. letting the LLM figure it out. The LLM cannot figure it out without explicit guidance that the failure is syntactic, not semantic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T17:53:45.976099+00:00— report_created — created