← Latest papers
🤖 AI

Learning to Rewrite Tool Descriptions for Reliable LLM-Agent Tool Use

This contribution introduces Trace-Free+, a curriculum-learning framework with an associated high-quality dataset that improves the reliability of LLM agents by rewriting tool descriptions to resolve ambiguities, thereby significantly enhancing scalability and generalization across large tool catalogs without per-tool retraining.

Original authors: Ruocheng Guo, Kaiwen Dong, Xiang Gao, Kamalika Das

Published 2026-04-30
📖 5 min read🧠 Deep dive

Original authors: Ruocheng Guo, Kaiwen Dong, Xiang Gao, Kamalika Das

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 Problem: The Dilemma of the "Bad Manual"

Imagine you hire a brilliant, super-smart robot assistant (the LLM Agent) to do your household chores. You give it a huge toolbox containing 150 different tools (like a drill, a hammer, a saw, and a blender).

The robot is smart, but it cannot read your mind. It must rely entirely on the instruction manuals attached to each tool to know what to do.

The problem? The original manuals were written for human engineers, not for robots.

  • Human Manuals: They are vague. They say things like "Use this for drilling," but they do not specify what kind of drill bit to use, how hard to press, or what happens if you try to drill into glass. They assume the human already knows the basics.
  • The Robot's Struggle: When the robot tries to use these vague manuals, it gets confused. If you ask it to "drill a hole in the wall," it might choose the wrong tool, use the wrong setting, or damage the wall because the manual did not say: "Do not use on glass."

The larger the toolbox gets (from 10 tools to over 150), the worse the confusion becomes. The robot starts guessing, and its success rate drops because the instructions are too noisy and ambiguous.

The Old Way: The "One-Tool-at-a-Time" Solution

Previous attempts to fix this were like hiring a team of editors to rewrite the manual for each tool individually.

  1. You would try to use the tool.
  2. If the robot failed, they would write down why it failed.
  3. They would then rewrite the manual for that specific tool to prevent that specific error.

Why this failed:

  • It is too slow: If you have 1,000 tools, you must go through this entire process 1,000 times.
  • It does not scale: If a brand-new tool arrives that the editors have never seen, they cannot fix it until they try it out and fail first.
  • It is repetitive: The editors keep learning the same lessons (e.g., "Always specify the exact date format"), but they do not teach the robot how to recognize these patterns itself.

The New Solution: "Trace-Free+" (The Pattern Learner)

The authors propose a new system called Trace-Free+. Instead of fixing tools one by one, they teach a "Super Editor" (a specialized AI model) to learn the universal rules of good instruction manuals.

Imagine you are teaching a chef how to write a cookbook.

  • The Old Way: You try every single dish, find the mistake, and rewrite that one recipe.
  • The New Way (Trace-Free+): You let the chef try hundreds of dishes and notice that every time a recipe is vague about "salt," the dish fails. The chef learns the pattern: "Good recipes must always include exact measurements."

Once the chef has learned this pattern, they can write a perfect manual for a brand-new tool they have never seen before simply by looking at the tool's basic specifications (the "schema"). They do not need to try the tool first.

How It Works: The "School Curriculum" Analogy

The paper uses a clever training method called Curriculum Learning. Imagine the Super Editor as a student going to school:

  1. Early Grades (Trace-Rich): The student receives a tool, a vague manual, and a video recording (a "trace") of a robot trying to use it and failing. The student learns: "Ah, the robot failed because the manual did not say that the tool only works with IPv4 addresses, not IPv6." The student learns the connection between the error and the missing instruction.
  2. Graduation (Trace-Free): As the student gets smarter, the teacher stops giving them video recordings. Now, the student receives only the basic specifications of the tool and must write the perfect manual without having seen a failure beforehand.
  3. The Result: Since the student learned the patterns in the early grades, they can now immediately write perfect manuals for every new tool without needing to see a failure first.

What They Found (The Results)

The authors tested this on real-world tools (like movie databases and music streaming APIs) and found:

  • It handles large toolboxes better: When the robot had to choose from over 150 tools, the old methods got confused and failed. The new method kept the robot on track, reduced errors by almost 30%, and made the robot successful 60% more often.
  • It works on new tools: The system did not need to be retrained for new tool types (e.g., switching from movie APIs to music APIs). It simply applied the patterns it had already learned.
  • It helps the robot become smarter: Even if you train the robot itself to be better, providing these "rewritten manuals" makes it even better. It is like giving a smart student a better textbook; they learn faster.

The Conclusion

The paper argues that we have focused too much on making the "robot" smarter while ignoring the "manuals" it reads. By teaching an AI to recognize the patterns that make up a good instruction manual, we can make tool-using robots much more reliable, especially when they must choose from a huge list of options.

In short: Do not just make the robot smarter; teach it how to read a better map. And the best way to do this is to teach the mapmaker to recognize the common mistakes people make when writing maps.

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 →