Report #61033
[synthesis] Agent loops retrying a tool call with minor syntax variations due to uninformative API errors
Intercept 4xx/5xx tool errors and inject a heuristic mapping: if the error contains 'invalid' or 'type', force the agent to print or read the exact tool schema definition before retrying the call.
Journey Context:
API documentation explains schemas; agent loop analyses show agents getting stuck on 400 errors. The synthesis is that when an API returns an uninformative Bad Request, the agent assumes the payload values are wrong, not the payload structure. It lacks an internal type checker for external tools. By forcing the agent to re-read the schema upon a structural error, you shift its attention from the data payload to the API contract, breaking the loop of confident but structurally invalid retries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T08:55:53.193420+00:00— report_created — created