← Latest papers
🤖 AI

Proper Scoring Rules for Agentic Uncertainty Quantification

This paper introduces the Trajectory Proper Score (TPS), a strictly proper scoring rule that rigorously elicits the full prefix-conditioned success-probability trace for language model agents, addressing the limitations of existing metrics that fail to distinguish between ranking performance and probabilistic truthfulness in agentic uncertainty quantification.

Original authors: Suresh Raghu, Satwik Pandey, Shashwat Pandey

Published 2026-05-26
📖 5 min read🧠 Deep dive

Original authors: Suresh Raghu, Satwik Pandey, Shashwat Pandey

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

Imagine you are watching a robot agent try to solve a complex puzzle, like navigating a maze or answering a tricky riddle. As the robot works, it doesn't just give a final answer; it talks to itself, makes moves, checks its work, and occasionally says, "I think I'm going to get this right," or "I'm not sure anymore."

For a long time, researchers have tried to grade these robots on how well they express that uncertainty. But this paper argues that the current grading systems are like judging a chef only by whether they got the order right, without tasting the food to see if they actually knew how good it was.

Here is the paper's core idea, broken down with simple analogies:

1. The Problem: Judging the "Rank" vs. The "Truth"

Currently, most tests for these robots look at ranking.

  • The Analogy: Imagine a teacher grading a student's study habits. The teacher looks at the student's final exam score. If the student who studied the most got the highest score, the teacher says, "Great! The study method works!"
  • The Flaw: The teacher doesn't care if the student thought they had a 99% chance of passing when they only had a 50% chance. The student might have been wildly overconfident but still got lucky.
  • The Paper's Point: Existing tests (like AUROC or Trajectory ECE) are like that teacher. They check if the robot's confidence ranks the right answers higher than the wrong ones. But they don't check if the robot's specific numbers (e.g., "80% chance") actually match reality. A robot can be a great "ranker" but a terrible "truth-teller."

2. The Solution: The "Trajectory Proper Score" (TPS)

The authors introduce a new grading system called TPS.

  • The Analogy: Instead of just looking at the final exam, TPS is like a coach who watches the robot step-by-step. Every time the robot makes a move, the coach asks: "You said there was a 70% chance of success from this point. Was that honest?"
  • How it works: The paper uses a mathematical tool called a "Strictly Proper Scoring Rule." Think of this as a penalty system that only works if you tell the truth.
    • If you say "90%" and you fail, you get a huge penalty.
    • If you say "50%" and you fail, you get a small penalty.
    • The only way to get the best possible score is to say exactly what the odds really are.
  • The Result: TPS forces the robot to be honest about its chances at every single step of the journey, not just at the end.

3. The "Censored" Problem: When the Game Stops Early

Sometimes, the robot runs out of time or hits a limit before it finishes the task. In the old days, researchers would just throw away these unfinished attempts.

  • The Analogy: Imagine a marathon runner who collapses at mile 20. If you only count the people who finished the race, you miss the data about the runners who struggled.
  • The Paper's Fix: The authors created a way to grade these "unfinished" runs fairly. They use a technique called "conditional projection."
    • Simple version: If the robot stops early and we don't know if it would have succeeded, the system assumes the worst (it failed) to be safe.
    • Advanced version: If we can estimate the odds of it succeeding if it had continued, the system uses that estimate to grade the unfinished run fairly.
  • Why it matters: The paper found that on a shopping task (WebShop), almost half the attempts were cut short. If you ignore them, you get a wrong picture of how the robot performs. When they included these "cut short" attempts, the robot's grade actually changed significantly.

4. The Big Discovery: Recalibration Changes Everything

The authors ran experiments where they took a robot's raw confidence numbers and "recalibrated" them (fixed them to be more honest).

  • The Analogy: Imagine a weather forecaster who always says "90% chance of rain." If it rains 90% of the time, they are a "good ranker" (they correctly predict rain days). But if they say "90%" when it's actually only a "50%" chance, they are a bad "truth-teller."
  • The Result: When they fixed the robot's numbers to be more honest:
    • The old tests (ranking) barely noticed a change. The robot still "ranked" the right answers best.
    • The new test (TPS) saw a massive improvement. The robot was now telling the truth about its chances.
  • Why this is a big deal: If you are using a robot to decide whether to call a human for help (a "handoff"), you need to know the real probability, not just the rank. If the robot thinks it's 90% sure but is actually only 50% sure, you might not call for help when you should.

Summary

This paper says: Stop grading robots just on who they think will win. Start grading them on whether they actually know the odds.

They built a new scoreboard (TPS) that:

  1. Checks the robot's confidence at every single step.
  2. Rewards honesty over just being "lucky" or "ranked high."
  3. Can handle situations where the robot runs out of time without throwing away the data.

The experiments show that using this new scoreboard reveals big mistakes in how robots express uncertainty that the old scoreboard completely missed.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →