Report #27333
[synthesis] Tool call succeeds on GPT-4o but Claude refuses to invoke the same tool, citing missing or ambiguous parameters
For cross-model tool schemas, make every optional parameter truly optional with explicit defaults in the description. Add guidance in the tool description for what the model should do when a parameter value is uncertain—do not rely on the model to improvise. For Claude, also include a system-level instruction: 'If a required parameter is truly unknowable, use the value UNKNOWN rather than skipping the tool call.'
Journey Context:
GPT-4o will often infer reasonable values for ambiguous or missing optional parameters and proceed with the call. Claude is more conservative—it may refuse to invoke a tool if it cannot confidently populate required fields, or it may emit a text block asking for clarification instead of making the call. This is not a bug but a behavioral fingerprint rooted in Constitutional AI training. The fix is not to weaken Claude's caution but to strengthen your tool definitions: add defaults, clarify in descriptions, and provide an escape hatch like UNKNOWN so the agent never stalls on a tool it could have usefully called.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T00:16:23.974262+00:00— report_created — created