Report #50636
[synthesis] Parallel function calling causes parameter cross-contamination where arguments intended for one tool are bound to another due to attention head overlap in similar schema descriptions
Disable parallel tool calling \(parallel\_tool\_calls=false\) when tool schemas share >30% parameter name overlap or semantic similarity; implement sequential execution with explicit state dependency declarations between tool calls.
Journey Context:
Parallel function calling assumes tool independence, but transformer attention mechanisms blend representations of similar schemas. When Tool A and Tool B both have parameters named 'id' or 'target', the attention heads create cross-activation patterns that cause argument misbinding \(similar to variable capture in closures\). Disabling parallelism introduces latency, but the 30% overlap threshold \(measured by Jaccard similarity of parameter names and descriptions\) provides a heuristic for when the risk of misbinding exceeds the cost of sequential execution. Explicit state dependencies force the model to acknowledge data flow between tools, reducing ambiguity in parameter binding.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:28:38.862182+00:00— report_created — created