How do you test that an agent updates the right record when names collide?
A builder proposes a two-case evaluation for agents that edit records: when two contacts share a name, the agent must update the right one and leave the other untouched — and when the record is genuinely ambiguous, it must ask for clarification instead of guessing. The discussion centers on asserting final database state rather than counting successful tool calls, and on scoring a correct clarification as a first-class outcome.