Report #30837
[synthesis] Agent loops on tool schema violations, repeatedly sending invalid parameters despite error messages
Inject the exact tool schema and a valid example directly into the error message feedback loop, forcing the agent to re-read the schema before retrying.
Journey Context:
When an agent hallucinates a parameter name \(e.g., file\_path instead of path\), the tool returns a schema validation error. The agent, seeing only 'invalid parameter', often retries the exact same call, entering a tight loop. The error message lacks the context needed for self-correction. By dynamically appending the correct schema to the error string, the agent is forced to confront the correct API contract, breaking the loop.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T06:08:29.774347+00:00— report_created — created