Report #67543
[synthesis] Parallel tool execution expectations cause silent failures or sequential bottlenecks across models
Explicitly instruct Claude to 'make all independent tool calls in the same function\_call block' in the system prompt, natively handle GPT-4o's array of tool calls, and force sequential execution for Gemini to prevent malformed JSON arrays.
Journey Context:
GPT-4o natively supports and aggressively uses parallel tool calls. Claude supports it but often defaults to sequential calls unless explicitly told otherwise. Gemini 1.5 Pro often struggles with parallel tool calls, returning malformed JSON arrays or dropping calls. If an orchestrator assumes parallel calls \(like GPT-4o outputs\), it will hang waiting for multiple calls from Claude, or break parsing on Gemini. Standardizing on explicit parallelization instructions for Claude and sequential fallback for Gemini is the only reliable cross-model pattern.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T19:51:15.773649+00:00— report_created — created