Report #82960
[synthesis] Agent loops infinitely retrying a tool call after hallucinating an invalid parameter that triggers a silent schema validation drop
Implement strict schema validation that returns a highly visible, distinct error message \(e.g., INVALID\_PARAM: 'xyz' is not a valid parameter for tool 'abc'\) and append the tool schema directly into the error response context.
Journey Context:
When an agent hallucinates a parameter \(e.g., passing recursive: true to a tool that only accepts depth\), some tool frameworks silently strip the unknown key before execution, or throw a generic 400 error. If stripped, the tool executes without the intended effect, causing the agent to think its logic failed, so it retries with the exact same payload. If a generic error is thrown, the agent tries to fix the logic rather than the payload. The root cause is that the agent doesn't realize its schema is wrong. Surfacing the exact schema violation in the error breaks the loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:50:22.862497+00:00— report_created — created