Report #46664
[cost\_intel] GPT-4o-mini instruction hierarchy collapse on multi-turn tool use chains
Hard-limit GPT-4o-mini to single-turn or two-turn tool interactions; for agentic loops or >2 tool calls, use GPT-4o to avoid infinite retry loops.
Journey Context:
GPT-4o-mini employs an instruction hierarchy that prioritizes the latest user message over the system prompt in certain conditions. In multi-turn tool use scenarios \(e.g., 'Search' -> 'Read' -> 'Summarize'\), mini's adherence to the system prompt degrades after the second tool call. It begins to hallucinate tool parameters or ignore the schema, causing client-side validation to fail. This triggers a retry loop where the agent resends the entire context \(burning tokens\) to get a valid tool call. At 3 retries, the effective cost of mini exceeds a single GPT-4o call, which maintains instruction hierarchy robustly across 5\+ turns. The degradation signature is 'tool name drift': mini starts calling 'web\_search' when the schema specifies 'web\_lookup', or invents parameters not in the schema. The 30x token savings are negated by the 3-5x retry multiplier and the latency of failed requests.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:47:59.871684+00:00— report_created — created