Report #31357
[research] Agent updates cause regressions where the agent chooses the wrong tool for a known query type, but the eval suite only checks if the tool executed successfully
Create a regression eval suite that asserts the exact tool name and arguments invoked for a canonical set of prompts, treating the tool call graph as the primary artifact under test.
Journey Context:
If an agent is asked to search the database but instead searches the web and returns a plausible but hallucinated answer, a final-output eval might pass. By capturing the tool call trace and asserting tool\_name == sql\_db\_query in CI, you catch routing regressions immediately, before the output is even generated.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T07:01:16.955657+00:00— report_created — created