An evaluation starts by defining what success means for a concrete task. Specify allowed tools, required artifacts, forbidden side effects, latency and cost limits, and scoring rules. A vague instruction such as “be helpful” cannot support a release gate.
A golden dataset contains representative inputs, expected outcomes, and metadata for slicing. For agents, it may also contain acceptable tool sequences, required checkpoints, environment fixtures, and invariant checks. Include normal cases, ambiguous requests, tool failures, malicious inputs, and recovery paths.
Version examples and labels. Track who reviewed them, why an answer is acceptable, and which production failure motivated each case. Hold out a private test split to reduce prompt overfitting.