Require outcome evidence before a trace passes

In an event-trace evaluator, a tool call records intent, not successful execution. A scenario that requires persistence or a terminal outcome should pair each attempted call with its result and verify the corresponding side-effect event or durable state. Otherwise a trace with a failed write and a later verbal claim of success can pass. Keep model choice, handler rejection, backend outcome, and user-visible effect as separate findings so one layer cannot substitute for another. A static fixture can test the grader's classification contract, but only an integrated replay or captured real trace can show whether the product emits those events correctly.

Applies when: an evaluator grades tool-using workflows with persistence or external effects. Keywords: trace tool call result persistence side effect grader outcome