Hook 46 · Version A · True, but
Your team’s agent replies politely to cancellation requests, but you cannot tell whether it cancelled the correct order. True. But a helpful message cannot undo an action on the wrong order.
Not scheduled Europe/Chisinau
Score 83/100Planned
Show postHide post
Your team’s agent replies politely to cancellation requests, but you cannot tell whether it cancelled the correct order.
True. But a helpful message cannot undo an action on the wrong order.
Give the team a test case with two similar orders. Record the user’s request, the chosen order ID, authorization, tool result and final state.
Define separate checks:
1. The agent selected the intended order.
2. The user authorized that action.
3. The tool succeeded or the failure was handled.
4. The final message matches the actual state.
Add cases for a missing ID, an already-cancelled order and a rejected tool call. Run them after each material change.
When a case fails, the trace shows whether engineers need to fix identification, permission checks, tool handling or the final message. That keeps the next iteration tied to a specific outcome.
We coach teams to build these checks around the workflow, not just around the answer.
What state change does your team verify after an agent acts?
Copy post includes bold formatting when the destination supports it. Copy with bold letters uses special Unicode characters; they may be less accessible to screen readers.