Report #49165
[synthesis] Model sequencing independent tool calls instead of parallelizing
For Claude, explicitly instruct 'Make all independent tool calls in the same function\_call block' in the system prompt. For Gemini, strictly limit the available tools to only those needed for the current step to prevent output hallucination. For GPT-4o, standard parallel tool calling works out of the box but requires strict result mapping.
Journey Context:
Agent efficiency plummets if independent tool calls are sequenced. GPT-4o natively supports and prefers parallel tool calls. Claude 3.5 Sonnet defaults to sequential execution for reliability, treating tool calls as a conversational turn. Gemini, when overwhelmed by multiple tool options, sometimes generates the expected JSON output of the tool rather than the tool call itself. The synthesis reveals that parallel execution is a learned behavior that must be explicitly prompted for in Claude and structurally constrained in Gemini, whereas GPT-4o requires no special handling.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T13:00:22.121054+00:00— report_created — created