Not All Proofs Are Equal: Evaluating LLM Proof Quality Beyond Correctness
This paper introduces ProofRank, a benchmark that evaluates large language models on five scalable dimensions of mathematical proof quality—conciseness, computational ease, cognitive simplicity, diversity, and adaptivity—revealing significant trade-offs between these qualitative metrics and mere correctness.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
The Big Idea: It's Not Just About Getting the Right Answer
Imagine you are a math teacher grading a student's homework. For a long time, you only cared about one thing: Did they get the right number at the end? If the answer was "42," the paper was marked correct. If it was "43," it was wrong.
But the authors of this paper argue that this is like judging a chef only by whether the food is edible. Sure, the food might be safe to eat (correct), but is it delicious? Is it easy to eat? Did the chef use a sledgehammer to crack a nut?
The paper introduces a new way to grade Large Language Models (LLMs) on math problems. They built a "report card" called PROOFRANK that doesn't just ask, "Is it right?" but asks, "Is it good?"
The Five Ways to Grade a "Good" Proof
The researchers identified five specific qualities that make a proof useful and elegant, comparing them to different aspects of a journey:
Conciseness (The "No Fluff" Rule):
- The Analogy: Imagine two people giving you directions to a coffee shop.
- Person A says: "Okay, so you leave your house, you walk down the street, you pass the red house, you pass the blue house, you pass the green house, you pass the yellow house, then you turn left..." (This is 500 words long).
- Person B says: "Walk two blocks, turn left." (This is 10 words).
- The Goal: Both get you to the coffee shop, but Person B is better because they didn't waste your time. The paper measures if the AI cuts out the unnecessary chatter.
- The Analogy: Imagine two people giving you directions to a coffee shop.
Computational Ease (The "Calculator vs. Brain" Test):
- The Analogy: Imagine you need to move a heavy couch.
- Method A: You hire 50 people to carry it one inch at a time, counting every step. It works, but it's exhausting and tedious.
- Method B: You use a dolly and a ramp. It's the same result, but much less "grind."
- The Goal: The paper checks if the AI is doing the math the hard way (brute force) or finding a clever shortcut that requires less mental "sweat."
- The Analogy: Imagine you need to move a heavy couch.
Cognitive Simplicity (The "Aha! Moment" Factor):
- The Analogy: Think of a magic trick.
- Trick A uses a complex machine with 50 gears that no one understands. It works, but it's confusing.
- Trick B uses a simple sleight of hand that makes you go, "Oh! I see how that works!"
- The Goal: The paper measures if the proof uses ideas that are easy for a human to follow and understand, rather than requiring a PhD to decode the logic.
- The Analogy: Think of a magic trick.
Diversity (The "Toolbox" Check):
- The Analogy: Imagine a carpenter who only has a hammer. They can build a house, a table, and a fence, but they are just hitting everything with a hammer. A master carpenter has a saw, a drill, a plane, and a hammer.
- The Goal: The paper checks if the AI can solve the same problem in many different ways (using a saw, a drill, etc.) or if it just repeats the same "hammer" approach every time.
Adaptability (The "Follow Instructions" Test):
- The Analogy: You ask a chef, "Make me a sandwich, but you must use a specific type of bread."
- Chef A ignores you and uses whatever bread they want.
- Chef B uses exactly the bread you asked for.
- The Goal: The paper tests if the AI can solve a problem while strictly following a specific method you requested (e.g., "Solve this using geometry, not algebra").
- The Analogy: You ask a chef, "Make me a sandwich, but you must use a specific type of bread."
The Experiment: The "Final Answer" Game
To test this, the researchers didn't just ask the AI to write a long essay. They used a specific type of math problem called a "Final-Answer Problem."
- How it works: The AI has to solve a hard math problem (like from a high school competition) and write out the full proof, but the only thing that matters for the "Correctness" check is the final number in the box.
- Why? It's much easier to check if the final number is right than to check every single step of a long proof. This lets them test hundreds of problems quickly.
- The Filter: They only compared the "quality" of proofs that actually got the right answer. If an AI gave a beautiful, short proof but the wrong answer, it was disqualified. You can't have a "good" proof for a wrong answer.
What They Found (The Results)
When they ran 10 different top-tier AI models through this test, they found some surprising things:
- The "Smartest" isn't always the "Best": The model with the highest accuracy (getting the most answers right) wasn't always the one writing the shortest, easiest, or most diverse proofs.
- The "Verbose" Problem: One model (Gemini-3.1-Pro) was very good at getting the right answer, but its proofs were 3.5 times longer than necessary. It was like a student who wrote a novel just to say "2 + 2 = 4."
- The "Lazy" Problem: Another model (Qwen3.5) was very good at finding clever, short shortcuts (high "Computational Ease"), but it got the right answer less often. It was like a driver who takes the scenic route but sometimes gets lost.
- Different Models, Different Personalities: Some models were great at being concise but bad at following specific instructions. Others were great at variety but wrote very long proofs.
The Main Takeaway
The paper concludes that we need to stop treating all "correct" math proofs as equal. Just because an AI gets the right answer doesn't mean it's a good math partner.
If you want an AI to help you learn, you want Cognitive Simplicity (easy to understand).
If you want an AI to help you research, you want Diversity (new ideas).
If you want an AI to help you write a paper, you want Conciseness (no fluff).
The authors built PROOFRANK so we can measure these specific traits and help users pick the right AI for their specific needs, rather than just picking the one with the highest score on a "correctness" test.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.