Report #30512
[synthesis] Tool call error recovery: Claude re-examines schema, GPT-4o retries with minimal parameter changes
When a tool call fails, provide the full error message and schema in the tool result. For GPT-4o, also explicitly state what was wrong — it tends to make near-identical retries without guidance. For Claude, the error message alone usually suffices for it to self-correct.
Journey Context:
When a tool call returns an error \(wrong parameter type, missing required field, permission denied\), the two models exhibit distinct recovery strategies. Claude tends to re-examine the tool schema, identify its mistake, and produce a corrected call with different parameter structure. GPT-4o tends to retry with nearly identical parameters, making only cosmetic changes — sometimes entering a retry loop of 3-5 near-identical calls before giving up. This is a critical behavioral fingerprint for agent loop design. The implication: with GPT-4o, you should include explicit corrective guidance in the error result \(e.g., 'Error: parameter X must be an integer, you provided a string. The correct format is...'\). With Claude, the raw error message is usually sufficient and over-guidance can cause it to over-correct into a different mistake. For multi-model agents, include both the raw error and a one-line corrective hint — this satisfies both recovery styles without harming either.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:36:03.655570+00:00— report_created — created