The Flow has not summarised this story yet — read it at arXiv Machine Learning.
ToolRobustBench is a stage-wise diagnostic benchmark designed to evaluate and diagnose failures in tool‑calling agents, which are large language models that select tools, provide structured arguments, and interpret tool feedback. The benchmark aligns four perturbation families—tool‑interface, user‑intent, tool‑output/observation, and runtime‑environment—with the tool‑use pipeline, attributing failures to specific stages such as tool selection, schema grounding, argument binding, and feedback handling. Experiments across 15,456 instances, 7 models, and 16 local tools reveal that while overall performance is high, robustness degrades significantly, especially under tool‑output/observation perturbations, and mixed‑family perturbations produce non‑additive failure patterns.
arXiv:2608. 08700v1 Announce Type: new Abstract: Reliable evaluation of tool routing is critical as Large Language Models increasingly operate as autonomous agents.
arXiv:2607. 04686v1 Announce Type: cross Abstract: Tool calling is central to modern language model agents, but aggregate benchmark scores often hide where tool use fails.
arXiv:2606. 03852v1 Announce Type: cross Abstract: Large language models often generate code with bugs.
arXiv:2601. 05366v2 Announce Type: replace-cross Abstract: Large Language Models (LLMs) are increasingly deployed as agents that invoke external tools through structured function calls.
The paper "Can You Check That? The Checkability Boundary for Local LLM Network Automation" proposes a method called Touchstone that uses local small language models (SLMs) to generate network‑automation candidates and applies task‑specific intrinsic checks to reject incorrect outputs before escalating to a larger frontier LLM. By defining a task as checkable when a cheap, deterministic test can reject outputs violating a necessary correctness condition, the authors demonstrate that Touchstone achieves high end‑to‑end accuracy (98.6% on conflict detection and 93.8% on intent translation) while escalating only a small fraction of inputs. The study shows that local inference is preferable when precise, low‑cost checks are available, whereas tasks lacking such checks should rely on the frontier model.