Report #74424
[synthesis] Parallel tool calling execution assumptions cause sequential bottlenecks or state collisions
Design the agent loop to handle an array of tool calls per turn. If you want parallel execution, explicitly instruct the model: 'If there are independent tasks, call the tools simultaneously.' Do not assume the model will parallelize without instruction, except perhaps GPT-4o.
Journey Context:
A common bottleneck in agents is sequential execution. Developers assume all models will parallelize independent tasks. GPT-4o does it by default \(returning multiple in one block\). Claude 3.5 Sonnet historically preferred sequential calls but recently updated to support parallel, though it often still sequences them if there's any implicit dependency. Gemini supports parallel but often needs explicit instruction to do so.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T07:31:06.321843+00:00— report_created — created