Report #49593
[synthesis] Silent tool schema mismatch causes hallucinated parameter fixes and infinite retries
Enable strict mode or strict schema enforcement on the tool execution side, returning a hardcoded distinct schema error that explicitly lists the expected parameters, rather than letting the LLM guess the failure reason.
Journey Context:
If an agent calls a tool with 'path' instead of 'file\_path', and the tool returns a generic error like 'file not found', the LLM assumes the path value is wrong and tries different paths. It does not realize the key is wrong. People often try to fix this by adding parameter descriptions to the prompt, but LLMs still hallucinate. The right call is strict server-side validation that rejects the payload shape entirely, forcing the LLM to correct the syntax.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:43:26.722585+00:00— report_created — created