← Latest papers
🤖 machine learning

TIER: Trajectory-Invariant Execution Rewards for Multi-Step Tool Composition

The paper proposes TIER, a reward framework that leverages function schemas and runtime execution to provide dense, trajectory-invariant supervision for multi-step tool use, enabling large language models to achieve high accuracy on complex compositional tasks where existing trajectory-based methods fail.

Original authors: Anay Kulkarni, ChiaEn Lu, Dheeraj Mekala, Jayanth Srinivasa, Gaowen Liu, Jingbo Shang

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

Original authors: Anay Kulkarni, ChiaEn Lu, Dheeraj Mekala, Jayanth Srinivasa, Gaowen Liu, Jingbo Shang

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 teaching a very smart but inexperienced robot assistant how to solve complex problems by using a toolbox of digital tools (like checking the weather, looking up flight times, or booking a restaurant).

The problem is that when you ask the robot to do a simple task (like "check the weather"), it learns quickly. But when you ask it to do a chain of tasks (like "find my flight, see where I'm landing, check the weather there, and then find a restaurant"), the robot often gets confused and fails.

This paper introduces a new teaching method called TIER to fix this. Here is how it works, explained simply:

The Problem: The "Right Answer" Trap

Currently, there are two main ways to teach these robots, and both have flaws:

  1. The "Pass/Fail" Method (Outcome-Based): You only give the robot a reward if it gets the final answer right. If it makes a mistake in step 2 of a 5-step process, it gets zero points. It's like a student taking a math test who gets the first four steps wrong but guesses the final number correctly; they get an A. But if they get the final number wrong, they get an F, even if they did the first four steps perfectly. The robot never learns where it went wrong.
  2. The "Copycat" Method (Trajectory-Supervised): You show the robot a specific, pre-written "perfect path" to solve the problem. If the robot follows that exact path, it gets points. If it finds a different, equally valid way to solve the problem, it gets punished. This is like a teacher who only gives credit if a student draws a map exactly the way the teacher did, even if the student found a faster route. As tasks get more complex, there are more valid routes, so the robot gets punished more often and stops learning.

The Solution: TIER (The "Smart Inspector")

The authors propose TIER, which acts like a smart, automated inspector that checks the robot's work at every single step, without needing a pre-written "perfect path" to compare against.

Instead of asking, "Did you copy the teacher's path?" or "Did you get the final answer?", TIER asks four specific questions about every tool the robot tries to use:

  1. Format Check: "Did you write the request in the correct language (syntax)?" (e.g., Did you use the right brackets and commas?)
  2. Schema Check: "Did you ask for the right tool and the right information?" (e.g., Did you ask for a "Flight" tool when you needed one, and did you provide the flight number?)
  3. Execution Check: "Did the tool actually work?" (e.g., Did the computer successfully run the code without crashing?)
  4. Answer Check: "Did you solve the original problem?"

The Magic of TIER:
If the robot finds a different valid way to solve the problem (e.g., checking the weather before finding the flight, instead of after), TIER still gives it full credit, as long as the steps are valid and the final answer is correct. It doesn't care about the order, only that the logic holds up.

The Analogy: Building a House

Imagine you are building a house.

  • Old Method 1 (Pass/Fail): You only pay the builder when the house is finished. If the roof collapses because the foundation was weak, you don't pay them anything. The builder doesn't know why they failed.
  • Old Method 2 (Copycat): You give the builder a blueprint and say, "Only build it exactly like this." If they decide to put the garage on the left instead of the right (which is fine), you refuse to pay them.
  • TIER Method: You have an inspector who checks every stage.
    • "Is the foundation level?" (Format)
    • "Did you use the right materials for the walls?" (Schema)
    • "Did the wall stand up?" (Execution)
    • "Is the house livable?" (Answer)
    • If the builder builds the garage on the left, the inspector says, "Great job, that's a valid house!" and pays them.

The Results

The researchers tested this on a new benchmark called DepthBench, which measures how well robots can handle tasks of increasing complexity (from 1 step up to 6 steps).

  • Old methods: The robots worked great for 1-step tasks but failed miserably once the task got to 4 or 5 steps. Their accuracy dropped to near zero.
  • TIER: The robots using TIER maintained over 90% accuracy even on the hardest 6-step tasks. They learned to chain tools together reliably because they got helpful feedback at every step, not just at the end.

Why This Matters

This approach means we don't need humans to write out thousands of "perfect" examples for every possible way to solve a problem. The system can automatically check if the robot is doing things correctly based on the rules of the tools themselves. This makes it much easier to teach AI agents to handle complex, real-world jobs that require multiple steps.

The paper concludes that for AI to get good at complex, multi-step reasoning, we need this kind of detailed, step-by-step feedback that rewards valid solutions, not just specific solutions.

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 →