Evaluation Prompt Engineering: Designing Reliable LLM Judges › Summary

Evaluation prompt engineering determines the quality of everything downstream in an LLM-based evaluation pipeline. The key principles from this chapter are:

• Prompt sensitivity is real and measurable. Small changes to phrasing, criteria ordering, and output format can change judge verdicts. Test your evaluation prompts across paraphrase variants before deploying them, and require high inter-variant agreement as a condition for use.
• Task description quality matters. Include the original user question, an explicit definition of the dimension being measured, and a description of the standard for high-quality responses. Vague descriptions produce unreliable judges.
• Explicit scale anchors reduce variance. Rubric-style criterion definitions with anchor descriptions at each scale point reduce the ambiguity that drives score variance. Endpoint descriptions (what a 1 looks like, what a 5 looks like) have the most impact.
• Few-shot examples improve calibration. Well-chosen examples that span the scale and cover borderline cases reduce sensitivity to phrasing variation and improve agreement with human raters. Quality matters more than quantity: two high-quality examples outperform five mediocre ones.
• Chain-of-thought formats improve consistency. Asking the judge to reason before scoring reduces sampling variance and produces verdicts that are more explainable and easier to audit.
• Multi-dimension evaluation requires separate criteria. Aggregated scores that combine multiple quality dimensions are hard to interpret and easy to game. Evaluate dimensions independently and combine them with explicit weights.
• Consistency testing is mandatory. Run the judge multiple times on borderline cases, measure agreement across runs, and set a minimum agreement threshold before trusting judge outputs in production.
• Score distributions require monitoring. As model quality improves over time, score distributions shift toward the high end of the scale. Recalibrate your judge periodically to maintain discriminative power across the response quality range you care about.

Evaluation prompt engineering is not a one-time task. It is an ongoing practice that requires monitoring score distributions, updating few-shot examples as model outputs evolve, and periodically validating judge verdicts against human labels. The investment pays off in evaluation pipelines that measure what you care about, rather than whatever the judge finds easiest to measure.