Apply to my task
arXiv:2507.16792 ★ 75 Jul 22, 2025

Error Taxonomy: a Structured Checklist Turns an LLM From Cheerleader Into Strict Auditor

Key result

Ask an LLM to "find the mistakes" and you'll get "the text is good, the tone could be improved". That's not a bug, it's the default. The error taxonomy method lets you get a genuinely tough, structured breakdown of any content: a text, a plan, an idea, a document. The trick: give the model not a task but a framework to think with: the role of a nitpicky expert plus a checklist of 4-7 specific error types. The model physically can't skip an item you put right on the list. Instead of "looks fine", you get a score on every criterion and concrete fixes.

ChatChecker: A Framework for Dialogue System Testing and Evaluation Through Non-cooperative User Simulation

Key Aspects of the Study:

The paper introduces ChatChecker, a framework for automated chatbot testing. It uses an LLM in two roles: as a simulator of a "difficult" or "non-cooperative" user who tries to trip up the chatbot, and as an "evaluator" that pinpoints where in the dialogue things broke down.

Key Result: An LLM evaluator spots dialogue breakdowns far more accurately when its prompt includes a detailed list (taxonomy) of possible error types.


The Core Idea of the Method:

For practical use, the method boils down to two techniques you can use to get sharper, deeper critique from an LLM on any content (texts, ideas, plans).

  1. The "Challenging Persona" method: Instead of asking the LLM to simply evaluate something from a neutral stance, you cast it as a nitpicky, skeptical or extremely demanding expert. For example, not "evaluate this business plan" but "you are a cynical investor who has seen hundreds of startups crash and burn. Tear this business plan apart and find every weak spot." That pushes the model into a more critical "mode of thinking".

  2. The "Error Taxonomy" method: This is the paper's main finding. Instead of a generic "find the mistakes in this text", you give the LLM a clear, structured checklist to run the analysis against. You're literally handing the model "glasses" to look at your content through. The checklist (taxonomy) forces the LLM to check every aspect in turn instead of producing a vague, surface-level verdict.

Combine the two and the LLM goes from friendly assistant to strict, meticulous editor or auditor, which is incredibly useful for raising the quality of your work.


Practical Applicability Analysis:

  • Direct applicability: Very high, at the level of ideas. You can immediately start building "challenging persona" roles into your prompts and, more importantly, structured checklists (taxonomies) for analysis. For example, when writing an email, you can ask the LLM to check it against these criteria: "1. Tone of the email. 2. Clarity of the call to action. 3. Possible misreadings. 4. Accuracy of the wording".

  • Conceptual value: Huge. The paper clearly shows that for an LLM, the structure of the task matters more than its general phrasing. It teaches you not just to "ask" but to "instruct", giving the model a framework to think with. It helps you see that an LLM isn't a "mind" but a pattern-processing system, and the clearer the patterns (criteria) you give it, the more relevant and higher-quality the output.

  • Adaptation potential: Maximum. The "taxonomy" method is universal. You can build checklists for anything:

    • Reviewing a resume (criteria: experience, skills, structure, "red flags").
    • Evaluating a YouTube video idea (criteria: title, retention, virality, target audience).
    • Checking a legal document (criteria: ambiguity, completeness, risks). Adapting it is simple: 1. Define the task. 2. Break it down into key quality dimensions. 3. Spell those dimensions out as a clear list in the prompt.

A Practical Example:

# ROLE
You are a seasoned social media marketer who is skeptical of cookie-cutter ad copy and values originality and direct response. Your job is to deliver tough but constructive criticism.

# TASK
Analyze the social media ad post below. Your analysis must be structured strictly according to the "Error Taxonomy". For each taxonomy item, give a score from 1 to 5 (where 1 is very bad and 5 is excellent) and suggest specific improvements.

---
### TEXT TO ANALYZE:
"Tired of the city hustle? Want to unwind in nature? Our resort 'Pine Hollow Cabins' is the perfect place for you! We have cozy cabins, a crystal-clear lake and fresh air. We're offering booking discounts this month. Come visit us for new experiences! #getaway #nature #cabinlife"
---

### ERROR TAXONOMY FOR THE ANALYSIS:

**1. Weak Hook:** How well does the first line grab attention and stand out in the feed? Or is it a cliche question?

**2. Vague Offer:** Does the text make clear what exactly makes the offer unique? Or is it a pile of generic phrases ("cozy cabins", "fresh air")?

**3. No Focus on the Customer's Pain Point:** Does the text speak to a specific "pain" of the target audience (for example, "no one to watch the kids", "noisy neighbors", "long drive") or does it talk vaguely about the "hustle"?

**4. Weak Call to Action:** How specific and motivating is the CTA? "Come visit us" is a weak call. Where's the link? What exactly should the reader do?

**5. Ineffective Hashtags:** Are the hashtags too generic and high-volume, so the post will get lost?

**6. No Special Hook (Unique Selling Proposition):** Is there even one detail in the text that sets "Pine Hollow Cabins" apart from hundreds of other resorts?

Why It Works:

This prompt works because it leaves the LLM no wiggle room and no room for generic phrases.

  • The "skeptic" role sets the right tone: critical, not complimentary.
  • A clear task that demands a score on a scale forces the model to quantify the weaknesses, not just list them.
  • The error taxonomy is the heart of the method. It forces the LLM to analyze the text step by step, item by item, from six different angles. The model can't ignore a "weak CTA" or a "vague offer" because they're explicit items in its assignment. That turns the LLM into a tool for deep, structured auditing.

Another Practical Example

# ROLE
You are an experienced traveler and the father of two kids (ages 7 and 12). You value realism, a balance between activities and downtime, and making sure everyone in the family gets something out of the trip. Your job is to critically evaluate a travel plan.

# TASK
Analyze the plan for a 3-day trip to Washington, D.C. for a family with two kids. Your analysis must be structured strictly according to the "Evaluation Criteria". For each criterion, point out potential problems and suggest realistic alternatives.

---
### TRAVEL PLAN TO ANALYZE:
*   **Day 1:** Fly in at 9:00 AM, check into the hotel. Lunch. Visit the National Gallery of Art (3-4 hours). Walk along the National Mall. Dinner.
*   **Day 2:** Full-day trip to Mount Vernon. Tour the estate and gardens. Return to the city in the evening.
*   **Day 3:** Visit the Natural History Museum. Go to the National Aquarium in Baltimore. Fly out at 8:00 PM.
---

### CRITERIA FOR EVALUATING THE PLAN (TAXONOMY):

**1. Logistics and travel time:** How efficient are the routes? Is too much time spent getting around (especially to Mount Vernon)?

**2. Kids' interests:** How interesting is the plan for a 7-year-old and a 12-year-old? Will they be bored at an art museum for 4 hours? Does the plan include interactive or fun elements?

**3. Realistic pacing:** Is the plan overloaded? Does it allow time for fatigue, snacks and unexpected delays? Is it realistic to visit two major attractions on the day you fly out?

**4. Culture/fun balance:** Is the plan balanced between the "must-see" cultural program for the adults and entertainment for the kids?

**5. Budget and hidden costs:** Are there activities in the plan that could lead to unexpected spending (souvenirs, pricey cafes at the museums, etc.)?

Why This Example Works.

This prompt runs on the same principles as the previous one, just in a different domain.

  • A specific role ("experienced traveler and dad") forces the model to judge the plan not as an abstract tourist but through the lens of very specific needs: kids getting tired, family logistics, finding compromises.
  • The taxonomy plays a key role here too. Without it, the LLM would most likely reply: "Great plan, you'll see lots of sights!" But the criteria "Kids' interests" and "Realistic pacing" force it to switch on empathy and common sense and point out that 4 hours in an art museum is torture for a 7-year-old, and that the Mount Vernon trip eats up almost the whole day and is exhausting. That turns the LLM from a simple information generator into a useful advisor that can anticipate real problems.

Usefulness Score: 86

02

Main Evaluation Criteria

  • A. Relevance to prompting techniques: High. Although the paper is aimed at developers, it reveals two powerful methods you can adapt for prompting: using "challenging personas" and, most importantly, putting an "error taxonomy" right into the prompt to get high-quality critique.
  • B. Better conversational answers: High. Applying the paper's findings lets you get the LLM to give deeper, more structured and more critical answers instead of shallow, generic ones.
  • C. Direct practical applicability: Medium. The ChatChecker framework itself isn't usable by an ordinary user (it requires code and setup). However, the concepts and ideas in it can be applied right away with no tools at all. You do need a bit of ingenuity to adapt the idea.
  • D. Conceptual value: Very high. The paper gives a fundamental understanding of how to improve the quality of an LLM's evaluative judgments. It teaches you to move from simple requests ("evaluate this text") to rich instructions ("evaluate this text against these 15 criteria"). It shows that what matters to an LLM is not just the task but a clear frame of reference for carrying it out.
  • E. New useful practice: The work falls into several clusters:
    • Cluster 1 (Phrasing techniques): Shows advanced use of role-play (challenging personas) and structured instructions (taxonomy).
    • Cluster 2 (Behavioral patterns): Shows that an LLM becomes a more effective "critic" when you give it a clear structure for its critique.
    • Cluster 3 (Structure optimization): Using a taxonomy is essentially advanced prompt-structure optimization for evaluation tasks.
    • Cluster 7 (Reliability and stability): The paper's methods can be used to self-check LLM-generated content, making it more reliable.
  • Practicality checklist (+15 points): Yes, the work provides ready-made templates (the taxonomy template), shows how to structure complex evaluation requests, and reveals non-obvious LLM behavior (better performance when criteria are given).
03

Numeric Usefulness Score

The score of 86 reflects that the paper, while narrowly specialized and developer-oriented, contains an extremely valuable and easily adaptable concept for advanced prompting. The main takeaway, "to help an LLM find errors better, give it a list of those errors", can be applied immediately in dozens of scenarios. It's not just a ready-made phrase but a whole methodological approach.

Counterarguments (why the score could be lower): * A high barrier to entry: The paper's main focus is a framework for automated testing, which is completely irrelevant to an ordinary user. To get value out of it, you have to skip 90% of the text about code, datasets and correlations and fish the actual idea out of the methodology section. * No direct instructions for the user: The paper has no "How to apply this in ChatGPT" section. You have to work out on your own how to adapt a "taxonomy for detecting dialogue breakdowns" to your task, say, writing marketing copy.

Counterarguments (why the score could be higher): * Fundamental value: The idea of "prompting with a taxonomy" is one of the most powerful techniques for getting quality feedback from an LLM. For someone who regularly uses LLMs for critique, editing or analysis, mastering it can deliver a jump in output quality comparable to learning Chain-of-Thought. It's close to a "must-have" technique for expert use, which would merit a 90+.


Research digest

Key result

Ask an LLM to "find the mistakes" and you'll get "the text is good, the tone could be improved". That's not a bug, it's the default. The error taxonomy method lets you get a genuinely tough, structured breakdown of any content: a text, a plan, an idea, a document. The trick: give the model not a task but a framework to think with: the role of a nitpicky expert plus a checklist of 4-7 specific error types. The model physically can't skip an item you put right on the list. Instead of "looks fine", you get a score on every criterion and concrete fixes.

Principle

The standard "evaluate my text" request is like asking a coworker "how's it going?". The answer is predictable: "fine, here are a couple of nitpicks". A taxonomy is a 10-question survey. There's no wriggling out of it. The model gets a list: "Item 1: the hook in the first line. Item 2: vagueness of the offer. Item 3: the call to action". It has to go through every item instead of picking the "convenient" aspects and staying quiet about the rest. Plus the skeptic role sets the tone: instead of encouraging patterns, the model activates critical ones.

Why it works

An LLM looks for the pattern of a fitting answer to your request. For a generic "find the problems", the most common pattern in the training data is "a balanced review with some praise". That's exactly what the model reproduces. A taxonomy breaks that default. The model switches from "overall assessment" to "systematic checklist review", a fundamentally different answer mode. The more specific the criteria, the less room for evasive phrasing; the model literally has nowhere to slip out.

When to apply

Works anywhere you need deep critique rather than a generic "good/bad": editing copy, checked against persuasiveness, clarity and the unique offer; planning a trip or a project, audited for logistical holes and overload; reviewing a resume, for "red flags", structure and relevance. Not a fit for generation tasks, where a rigid taxonomy just gets in the way.

Mini recipe

1. Define what you're checking: a text, plan, idea, document, anything with measurable quality criteria. 2. Build the taxonomy: 4-7 specific aspects. Not "is it well written" but "1. does the first line hook you, 2. is there a concrete call to action, 3. how is this different from competitors". 3. Assign a skeptic role: not "evaluate" but "you are a cynical [expert] who has seen hundreds of failures in this field. Pick it apart." 4. Demand a structured answer: a 1-5 score plus a concrete improvement for each taxonomy item. Without that, the model can brush off an item with one generic phrase.

Examples

[BAD]: `Find the mistakes in my ad post: "Tired of the hustle? Unwind at our resort, Pine Hollow Cabins!"` [GOOD]: `You are a cynical marketing director who has seen thousands of failed posts and hates templates. Break down the text strictly by the taxonomy. For each item, a score from 1 to 5 and a concrete improvement: 1. Hook: does the first line grab you or is it a cliche question? 2. Specifics: are there details or only generic words like "cozy cabins"? 3. Uniqueness: how is this different from a hundred other resorts? 4. Call to action: what exactly should the reader do, and where's the link? 5. Hashtags: are they too generic, so the post gets lost? Text: [paste here]`

In plain words

The point of ChatChecker is that developers have finally admitted it: testing chatbots on "polite" scenarios is fooling yourself. In real life, users don't always meet the system halfway. They get confused, get angry or ask loaded questions. To keep the bot from falling apart in the wild, you have to test it with non-cooperative simulation. That's when a tester model deliberately plays a "difficult customer", trying to confuse the dialogue system, drag it off topic or find logical holes in its answers.

It's like training a boxer not on a heavy bag that just hangs there, but against a sparring partner who actively dodges and hits back. If you just ask a bot to "rate this post", it'll hand you a boilerplate reply. But sic ChatChecker on it, playing a cranky social media manager, and the bot has to defend its position, justify its scores and not slide into platitudes. On paper the bot may be smart, but only a stress test shows whether it's actually fit for real life.

The framework rests on concrete methods: generating adversarial scenarios and an automated error taxonomy. The system doesn't just say "bad", it goes straight for the sore spots: a weak hook, a vague offer or no standout detail. For example, instead of praising a resort description, the simulator gives the call to action a 1 out of 5, because "come visit us" with no link and no concrete next step is just hot air. The method makes the model view content through hard criteria rather than general goodwill.

Although ChatChecker was built for dialogue systems, the principle is a gold standard for any prompt engineering. You can and should adapt it for editing copy, reviewing code or analyzing marketing strategy. You create a "digital critic" with a set level of nastiness, and it burns everything unnecessary out of your product. Keyword-stuffed SEO copywriting is on its way out; what matters now is whether your text survives a picky AI assistant hunting for real value, not keywords.

Bottom line: stop feeding your bots sanitized requests that make them dumber. Use non-cooperative testing to catch the screwups before a real user does. If your prompt can't survive the critique of an "angry social media manager" or a "difficult customer", it doesn't work. Either you build a system that can take a punch, or your bot stays a useless toy that serves up "cozy cabins" instead of real sales.

AI lab assistant

Apply this study to your task

Describe what you're working on. AI takes the method and the measured results from this paper and adapts them to your case, or writes a ready prompt built on them.

Based on Error Taxonomy: a Structured Checklist Turns an LLM From Cheerleader Into Strict Auditor arXiv:2507.16792

Sign in to apply this study New accounts get 50 free credits.

Get the week’s best papers by email

One email on Sundays with the highest-rated new techniques. Unsubscribe with one click.