Report #49153
[synthesis] Tool call JSON parsing fails due to unexpected keys added by the model
For Claude, explicitly state 'Do not add any keys not defined in the schema' in the tool description, as it frequently ignores additionalProperties: false. For GPT-4o, rely on strict: true to enforce exact schema adherence.
Journey Context:
GPT-4o's strict: true guarantees exact schema adherence by constraining the generation. Claude lacks an equivalent strict enforcement flag for tool schemas and frequently adds helpful but unparsable keys \(like 'reasoning' or 'status'\) even when additionalProperties: false is set. Gemini sometimes strips required keys if it cannot populate them. A cross-model agent must use API-level strictness where available \(OpenAI\) and prompt-level strictness where not \(Anthropic\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:59:18.137513+00:00— report_created — created