Report #73945
[synthesis] Parallel tool result interleaving causing attribution confusion
Enforce strict 'correlation ID' tracking: prepend each tool call with a unique ID in the prompt context, and require the agent to map each result back to its ID before using the data.
Journey Context:
When agents invoke multiple tools in parallel \(e.g., OpenAI's parallel function calling\), the results return in the same context window. Without explicit delimiters, the model can confuse which result belongs to which call—especially when results have similar schemas \(e.g., two 'user' objects from different APIs\). This creates 'binding errors' where the agent uses User A's data for User B's operation. Simple prompt engineering like 'be careful' fails because the confusion happens at the attention mechanism level, not the instruction level.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T06:42:45.854699+00:00— report_created — created