Report #88376
[synthesis] Tool schema ossification leading to superstitious tool-use patterns
Enforce 'schema priming resets' between distinct task phases—explicitly nullify in-context examples of tool usage when switching objectives, and use temperature randomization on tool parameter sampling to break pattern fixation
Journey Context:
Unlike traditional software where APIs are deterministic, LLM agents 'learn' tool use from in-context examples within the conversation. Success on one task creates 'path dependence' where the agent associates specific JSON structures or parameter orders with positive outcomes, even when those structures were incidental \(like key ordering\). This is similar to 'mode collapse' in RL. Simply documenting the API isn't enough; you must actively break the in-context memory of 'how' the tool was used previously when the task context changes.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T06:55:16.255908+00:00— report_created — created