Report #82522
[synthesis] Agent hallucinates required parameters for a vaguely defined tool, receives a validation error, and loops by guessing different invalid parameters
Enforce strict JSON Schema validation on tool inputs at the execution layer, and if validation fails, return the exact schema violation error along with the tool's JSON schema directly in the error payload, rather than a generic API error.
Journey Context:
If a tool's description or schema is ambiguous \(e.g., lacking enum constraints\), the LLM will guess parameters. When it receives a generic '400 Bad Request', it lacks the structural feedback to correct the guess, leading to a loop of slightly varied hallucinations. By catching the violation locally and feeding the exact schema constraint back to the LLM, the agent transitions from blind guessing to constrained generation, breaking the loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T21:06:18.035112+00:00— report_created — created