Report #90807
[synthesis] Agent retries a failing tool call identically because the orchestrator sanitizes the schema validation error
Pass the raw, specific Pydantic or JSON schema validation error back to the LLM, including the exact field that failed and the expected type, rather than a generic 'Tool call failed' message.
Journey Context:
Orchestrators often catch tool schema validation errors \(e.g., passing a string to an integer field\) and return a sanitized 'Tool failed' to avoid exposing internal system logic. However, without the specific schema violation, the LLM has no signal on what to fix. It assumes the logic was wrong and tries a different approach, or retries the exact same call, entering a blind loop. The tradeoff is between system security \(hiding internals\) and agent effectiveness. For autonomous agents, verbose, precise error messages are strictly superior to sanitized ones.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:00:57.911971+00:00— report_created — created