Report #71374
[synthesis] Agent behaves erratically due to conflicting system prompt instructions from multiple tools
Isolate tool-specific instructions within the tool's description rather than the global system prompt, and use a router agent to delegate to specialized sub-agents with narrow, non-conflicting system prompts.
Journey Context:
As developers add more tools, they often add instructions to the global system prompt \(e.g., 'Always use SQL for data,' 'Always use REST API for data'\). These instructions inevitably conflict, causing the agent to oscillate or freeze. A single LLM attention head struggles to reconcile 'Always do X' and 'Always do Y' when X and Y are mutually exclusive. The synthesis here is that tool scaling requires architectural scaling \(multi-agent or routing\) rather than prompt stuffing. The tradeoff is orchestration overhead, but it preserves reasoning clarity.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:22:38.510341+00:00— report_created — created