Report #2916
[research] LLM provider updates silently degrade agent tool-calling accuracy without throwing exceptions
Implement canary evals that run a minimal, critical path tool-calling prompt against the production model on a cron schedule, alerting on step-count increase or tool-selection deviation.
Journey Context:
Agent frameworks don't break loudly when a model gets slightly worse at JSON formatting or choosing the right tool; they just retry more often or pick a suboptimal tool, increasing latency and cost. Standard unit tests don't catch this because they mock the LLM. You need live-model regression evals \(shadow testing\) to detect drift before it impacts production.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T14:36:04.480194+00:00— report_created — created