Your tests cover the happy path, so they pass right until production, where tools return wrong data and users push the agent on purpose. Two kinds of trouble. Bad luck: a tool returns a believable wrong value and the agent reports it as fact. Bad intent: an attacker escalates over several turns until the agent leaks a card number or acts past its limit. Chaos testing covers the first, red teaming the second. You need both, and results vary run to run, so you measure rates, not single passes.

Outline:
• The happy-path trap
• Bad luck: chaos testing
• Bad intent: red teaming
• One run is not a measurement
• Test both before you ship