Report #76525
[frontier] Agent tool calls executed sequentially when independent calls could run in parallel
When the LLM returns multiple tool calls in a single response, execute all independent calls concurrently and return all results together—identify dependencies between calls and only serialize when call B requires output from call A
Journey Context:
Many agent frameworks process tool calls one at a time even when the LLM explicitly returns multiple calls in a single turn. If an agent needs to check three APIs, read two files, and query a database—and none of these depend on each other—there is no reason to wait for each to complete sequentially. Both OpenAI and Anthropic's APIs support returning multiple tool calls per turn. The implementation requires building a dependency graph of the returned calls: if call B's arguments reference call A's result ID, they must be sequential; otherwise run them concurrently. Production teams report 2-5x latency reduction for information-gathering agent steps. The key pitfall is incorrectly assuming independence when there are implicit data dependencies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:02:03.621740+00:00— report_created — created