← Back to concept explainers

Concept Fable

LLM evaluation

Conclusion first:LLM evaluation systematically measures the capabilities, limitations, risks and costs of an LLM or Agent on specific tasks through automated testing, human scoring, model judges, adversarial probes and online monitoring. It should cover accuracy, relevance, factuality, tool calling, format compliance, safety, latency, cost and business outcomes. The core value of enterprise eval is bringing model, prompt, RAG, tool and policy changes into a comparable, regression-testable and auditable quality loop.

LLM Evaluation (Eval) · Evaluation

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

After Changing the Ink and Brush, the Accounting Office Recalculated the Old Accounts First

The Qingwa trading firm had a clerk who could write letters, check accounts, and draft contracts. In the early years, the manager only looked at whether the letters he wrote were fluent and whether customers nodded. When business was light, this was enough to get by. After the firm expanded, the clerk had to handle collections, quotations, contract exceptions, customer complaints, and internal approvals. It looked like writing, but in reality every matter involved money, responsibility, and risk.

The proprietor's naive fix was to casually test three letters after each change of pen and ink. If all three went smoothly, he assumed the new pen and ink were better. Then one quotation letter omitted a discount condition, and the firm lost a large sum.

A later review found that the clerk was more polished on ordinary greetings, but had regressed on complex clauses, factual citations, and boundary refusals. The three sample letters did not cover the truly dangerous work.

The old accountant proposed not to keep testing by feel. First list the most common, most valuable, and most error-prone tasks of the firm, then prepare examples, standard answers, scoring rules, and failure levels for each type of task.

From then on, changing ink, changing paper, changing documentation habits, or changing ledger sources all had to run the same test suite. Results looked not only at the final text, but also at facts, citations, format, risk, cost, and whether human takeover was needed.

Some tests are auto-graded, some need a veteran's eye, and some are deliberate traps. When scores drop, you can't wave it through with 'it reads more naturally overall'; when scores rise, you also need to check whether safety and cost were sacrificed.

The firm gradually formed a closed loop: online errors enter the sample library, the sample library enters the release gate, and the gate result determines whether to launch, roll back or continue adjusting.

What stung the shopkeeper most was that the letter about losing money never appeared in casual testing at all. Yet it was exactly the scenario the firm encountered most often and lost money on most easily. The shopkeeper finally understood that every time the writing-and-answering clerk changed, it had to pass the gate again. Quality had to become a system, not rely on a one-time acceptance check. Later, the shopkeeper also learned to look at the cost behind the scores. Once, a new clerk was faster on most questions but vague when refusing overreach requests; another time, new ink and brushes made letters prettier but reduced cited sources. The old accountant insisted on putting these into the same acceptance ledger. What the firm needed was not one beautiful trial draft, but the ability to explain, with every change, which capabilities improved and which risks grew. Later, these mistaken cases were no longer hidden as embarrassments but entered the next round of test questions. The more the firm feared a type of error, the more it had to put that error at the gate and test it repeatedly.

Reveal

This story is about: LLM evaluation

LLM evaluation systematically measures the capabilities, limitations, risks and costs of an LLM or Agent on specific tasks through automated testing, human scoring, model judges, adversarial probes and online monitoring. It should cover accuracy, relevance, factuality, tool calling, format compliance, safety, latency, cost and business outcomes. The core value of enterprise eval is bringing model, prompt, RAG, tool and policy changes into a comparable, regression-testable and auditable quality loop.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • The clerk who can write letters and audit accounts: LLM application or enterprise Agent
  • Changing ink and paper: model, prompt, RAG, toolchain, or policy changes
  • Try three letters at random: temporary demos and small-sample subjective experience
  • Discount omitted from the quote letter: real business risk and high-cost failure
  • Samples, reference answers and scoring rules: eval dataset, rubric and scorers
  • Automated judging, master review, trap questions: automated evaluation, human evaluation, and adversarial evaluation
  • Wrong cases enter the sample library: production feedback flows back into regression evals
  • Final insight: LLM Evaluation turns every intelligent system change into a verifiable engineering decision

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

BenchmarkScoring metricsEval SuiteA/B evaluation

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号