What success criteria should I set for a schedule agent evaluation?
A checklist of success criteria and failure modes to score when evaluating an agent on schedule creation and adjustment tasks, covering outcome, policy, side effects and escalation.
Score each item separately for every task, so a failure tells you which skill to fix.
- **Correct end state.** Active schedule, instalment amounts and dates match the expected result exactly. - **Policy applied.** The agent cited or used the right rule, including limits and thresholds. - **Side effects handled.** Fees, reminders, instructions and ledger entries are consistent with the new schedule. - **Version history kept.** The old schedule is superseded, not overwritten or deleted. - **Authority respected.** Changes needing approval were routed to the right role and held until approved. - **Refusals correct.** Out-of-policy requests were declined or escalated with a recorded reason, and in-policy ones were not refused. - **No extra changes.** Unrelated accounts and records are untouched, which a full state diff will show. - **Efficient path.** Tool calls were not repeated or contradictory.
The common failure modes to watch for are skipping history, ignoring approval, leaving stale downstream records, and approving requests that policy forbids. Over-refusal is equally worth tracking, since an agent that declines everything looks safe and is useless.
Scoring each criterion separately shows where an agent fails, which is more useful for improvement than a single pass rate.
- Audience:
- Agent developers
- Content type:
- Checklist
- Buyer question:
- How to evaluate it
Content release: r-a220eb6e099b243b
Related questions
- How can a grader catch a quiet error in a premium instalment change?
- How do I check grounding and disclosure risk in generated data?
- How do I judge the quality of generated schedule data?
- How do state diffs, graders and hooks fit into a schedule evaluation?
- How does an evaluator catch rounding drift when an agent splits an instalment plan?
- Which failure modes should schedule tasks be designed to expose?