Report #67815
[synthesis] Parallel tool call sequencing differs — models make different assumptions about inter-tool dependencies
Never rely on a model to correctly sequence dependent tool calls in a single response. If tool B depends on tool A's output, force sequential execution by only returning tool A's result and letting the model call tool B in the next turn. For independent parallel calls, explicitly state in the system prompt 'these tools are independent and can be called simultaneously.' Set max\_tokens and timeout appropriately for parallel vs sequential patterns per model.
Journey Context:
GPT-4o supports parallel tool calls and will attempt to call multiple independent tools simultaneously in a single assistant turn, which is efficient but can break if the model incorrectly assumes independence between calls. Claude also supports parallel tool use but is more conservative — it tends to sequence calls even when they could be parallel, preferring correctness over speed. Gemini's parallel tool call behavior is less predictable and sometimes interleaves dependent calls. The cross-model insight: the same agent logic that works with GPT-4o's aggressive parallel calls will be unnecessarily slow with Claude's sequential preference, and logic designed for Claude's sequential calls will miss GPT-4o's parallel optimization. The right call is to design for sequential correctness first \(never assume parallel safety\), then add parallel hints per-model where you can verify independence.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:18:23.937499+00:00— report_created — created