正在加载视频...
视频加载失败
🚀We are excited to introduce the Tool Decathlon (Toolathlon), a benchmark for language agents on diverse, complex, and realistic tool use. ⭐️32 applications and 600+ tools based on real-world software environments ⭐️Execution-based, reliable evaluation ⭐️Realistic, covering daily and professional scenarios Toolathlon reveals significant shortcomings of SOTA LLMs in realistic... show more
44,403 次观看 • 10 个月前 •via X (Twitter)
14 条评论

Nice work, @junxian_he, @syz0x1, @gneubig & many others! Thanks for comparing with AppWorld! A couple of notes on it (your Table 1): The AppWorld row for "Avg # Turns" is "--" 👉 AppWorld tasks are very long-range in terms of # turns & # tool calls. See the histogram of tasks% requiring N tool calls is in our Fig. 5 (snapshots attached). They often go over 50. These solutions were written by us (to verify solvability), with near-perfect env apis knowledge; Sonnet typically takes more. Can share comparable Sonnet # turn stats/traj. soon offline. The AppWorld row for "Real States & Init" is X 👉 Each AppWorld task comes with its own initial state that is carefully & uniquely programmed (involving often 100+ LOCs) to ensure the task is hard to cheat, challenging, and realistic. We've thought quite carefully about designing each task's initial state, tailoring it to its unique requirements. Tab. 1, 8, 9 (snapshots attached). 👉 IMO, ensuring these good properties is what one needs. Sourcing data from real software can help with realism, but by itself, it is not enough, and there are other ways of achieving the desirable properties, as we did in AppWorld.

Hi Harsh, thanks for the clarification! For the "# Turns" sorry we missed the specific number in the paper, are the # turns and # tool calls the same in AppWorld? Shall we refer to Table 2 in App World that is 42.5 turns? For the "Real States & Init" column yeah we marked it as X because we noticed the initial state was programmed, but we agree it is a bit confusing there and we'll make necessary revision soon about this information.

Thank you, @junxian_he! Greatly appreciate your openness to revise that AppWorld information! 🙏 >> Re: Average # Turns That 42.5 number refers to the average tool calls in solutions that we wrote. It shows tasks are indeed quite long-horizon & complex. But this number isn't head-to-head comparable with the average turns in solutions that Claude wrote. Claude typically makes more tool calls than us, but then one turn can have multiple (parallel) tool calls. So I'm not sure which way the comparable number will go, and by how much. Note that we do have many task difficulty estimators (Figure 9), but none based on the Claude-based metric you have. I'm doing Claude and other model runs soon, and we will also release trajectories. I'll share the comparable stat from them with you then; it'd be wonderful if you could update the table in your next version with that. >> Re: we noticed the initial state was programmed Yes—the initialization function is indeed a program we manually wrote for each task. But this is quite similar to what you also do with your state-initialization scripts: you initialize your real apps with task-specific data, whereas we initialize our high-fidelity simulated apps. Concretely, we first generate a large-scale, realistic data simulating the digital activity of 100+ people over 2 years, resulting in ~350K rows & 100+ tables. Then, for each task, we manually write initialization functions (setup: 3.1) that adapt this base data as per task-specific requirements. Each task has its own unique requirements, not only to make it sensible/well-defined, but also hard to cheat, and challenging. Having just reread your paper again, I do really think it fits your description of realistic state inits. Sharing some snapshots from the talks I gave earlier and a link to the slides for more context (has speaker notes for details).

Performance of different models. Claude-4.5-Sonnet leads the race with 38.6% pass@1 accuracy, GPT-5 and Claude-4-Sonnet are following with similar performance. Toolathlon reveals a clear gap between open-source and proprietary models. DeepSeek-V3.2 is the best-performing open-source model with 20% pass@1 at a remarkably low cost, spending $5 in total

An example task

Each task in Toolathlon is based on real-world environments with dedicated state init (such as a prefilled email inbox and real-world financial google sheets), and is verifiable to ensure reliable eval. Most tasks require interleaving multiple applications to complete. The tasks take Claude-4-Sonnet 26.8 turns on average.

What fails the SOTA LLMs? We first analyze the tool call errors, some models just hallucinate non-existing tool names, for example Gemini2.5

Long context is a clear challenge for language agents. When tool returns are overlong, the success rates are generally lower than the tasks without overlong tool returns.

The cost-effectiveness of models is also very important. Claude is generally more expensive, whereas GPT-5 offers better cost efficiency among proprietary models. Among open-source models, DeepSeekv3.2 is the most affordable while achieving the highest performance.

Finally, check out our eval toolkit! We support parallel, containerized evaluation and running full evaluation of Claude 4.5 Sonnet takes 70 minutes. Our website ( also allows to explore all the tasks and trajectories!

This project is co-led by @lockonlvange Wenshuo Zhao, Jian Zhao, @AndrewZeng17 @HaozeWu7 , and a wonderful collaboration from all the collaborators from HKUST, @OpenHandsDev , CMU, and Duke: Xiaochen Wang, Rui Ge, @SArt_Maxine @yuzhenh17 @WeiLiu99 @junteng88716710 @SuZhaochen0110 Yiyang Guo, @FaZhou_998, Lueyang Zhang, Juan Michelini, @xingyaow_ @xiangyue96 @syz0x1 @gneubig !

Interesting to see how real-world scenarios expose the gaps in SOTA LLMs. Tool interleaving sounds tough for them.

nice work!

600+ tools sounds comprehensive for evaluating language agent capabilities.
