Report #40088
[synthesis] Models ignoring parallel tool call opportunities or failing on implicit dependencies
For GPT-4o, explicitly state in the tool description if it is independent to encourage parallelization. For Claude, if you want parallelization, you must often force it via system prompts \('Make all independent tool calls in the same block'\), otherwise it defaults to sequential for safety. For Gemini, parallelization is often a system-level feature, not a model inference.
Journey Context:
Agents built on GPT-4o often suffer from cascading failures because it parallelizes calls that share a mutable state \(e.g., two file writes\). Claude's sequential default is safer but slower. The synthesis is that 'agentic eagerness' is a model fingerprint: GPT-4o optimizes for speed \(parallel\), Claude optimizes for correctness \(sequential unless certain\). You must architect state management assuming GPT-4o will race, while architecting prompt instructions assuming Claude will stall.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T21:45:39.037347+00:00— report_created — created