Clicked Gallery

What is ToolGrad?

Highlighted from a real engineering doc. Explained by Clicked.

Used in a sentence

Engineering Notes · AI Systems

Google's ToolGrad writes the answer before the question, and 99.8% of its practice examples came out usable.

The reader highlighted one word in the docs. Clicked explained the technical term β€œToolGrad” in simple terms:

Explained in three depths

Same facts, different vibe β€” Slang mode 😎

The Clicked way

●○○

Overview

ToolGrad is a method from Google Research for making the practice examples that teach an AI model to call tools. Tool calling is the model writing a request to an outside tool, such as a search or a map, which the app (the harness, the software around the model) then runs. ToolGrad builds a working chain of tool calls first and writes the user's question afterwards, to fit the chain. Take a chain of two calls: find_pharmacy with open now as its one field, then get_directions. Only then is the question written: which pharmacy near me is open now, and how do I walk there? The older method wrote the question first and then searched for calls to answer it. Google counted 63.8% of its examples as usable, against 99.8% of ToolGrad's. Every question ToolGrad writes already has a chain of calls that answers it, because the chain was built first.
●○○

Overview

ToolGrad is Google's trick for making the practice questions that teach an AI to call tools, and the trick is doing it backwards. Tool calling is the AI asking an outside tool, a map or a booking site, to do a job it can't do itself. Making practice questions used to mean asking first and hoping later. Write a question, then set an AI agent loose to find tool calls that answer it. More than a third of the time, 36.2 in 100 (100 minus 63.8), it came back with nothing. ToolGrad skips the hoping. It runs the tools first: find_bike_shop, then check_hours for Sunday, then book_slot, 3 calls that already work. Then it writes the one question those 3 calls answer: can you get my bike fixed this Sunday? 😎

A quick take β€” often all you need.

●●○

Detail

ToolGrad is a method from Google Research for making the practice examples that teach an AI model to call tools, and it builds each example backwards: the chain of tool calls first, the user's question second. Tool calling is the model writing a request to an outside tool, such as a search or a calendar, which the app (the harness, the software around the model) runs before handing the result back. A model learns to do that from practice examples during training. ToolGrad runs before training, to make those examples. When you use the app (inference), only the trained model runs. Each example is a question, the right tool calls in order, and the final answer. Writing thousands of those by hand is too slow, so labs have an AI generate them, which is what synthetic data means. The older way started with the question. An AI agent then searched by trial and error for tool calls that answered it, and when no chain worked the example was thrown away. Google's count: 63.8% came out usable, so 36.2 in 100 were wasted. ToolGrad starts with the chain. It proposes a few tools that might help, tries them out, and has an AI judge write a short note on which call worked best. That note is the textual gradient. A gradient is the signal in training that says which way to adjust, and this one does the same job in words. The best call joins the chain and the loop runs once more. When the chain is complete, the AI writes the question and the answer to match it. Of those examples, 99.8% came out usable, and the chains were longer, 3.4 calls against 2.1. Google made 500 examples this way and trained its open model Gemma 3 12B (one anyone can download) on them. On BFCL, a test of tool calling, the model scored 83.1, which is 6.3 points above its score before that training and level with Gemini 2.5 Pro's 83.2 at the time. Two limits. The comparison with those models rests on one test and 500 examples. And a question written to fit an answer may not read as something a person would ask.
●●○

Detail

ToolGrad is how Google cooks up practice material that teaches an AI to call tools, and it's done in reverse: tool calls first, question last. Tool calling is the AI asking an outside tool, a search or a calendar, to do a job, and the app it lives in (the harness) running that tool. The AI picks that up in training, from a pile of examples, each one a question, the correct calls in order, and an answer. Here's why the order matters. Start from the question and you're betting that an answer exists. The old method lost that bet a lot: an AI agent went looking for tool calls to fit the question, and only 63.8 in 100 examples survived the hunt. ToolGrad doesn't bet. Try a handful of tools, have an AI judge jot a one-line note on which call actually worked, keep that one, go round again. The note is the whole textual gradient, a nod to the gradient (training's nudge saying which way to turn), except it's plain English rather than maths. Once the chain is long enough, the AI writes a question that chain answers. The chain already works, so 99.8 in 100 examples are usable, and because ToolGrad keeps adding calls, the chains run 3.4 calls on average rather than 2.1. Google generated 500 of these, trained its free-to-download Gemma 3 12B on them, and the small model hit 83.1 on BFCL, a tool-calling test, against GPT-5's 74.4 as of the paper. So 500 examples pushed a small free model past a flagship, on one test, and one test is the asterisk. A question written backwards can also read oddly, because it was shaped to fit its calls rather than typed by a person. 😎

Want more? One click digs deeper.

●●●

Analogy

ToolGrad is a method for making the practice examples that teach an AI model to call tools, and it builds the chain of tool calls first and writes the question afterwards. Setting a crossword works the same way. The setter fills the grid with words first and writes the clues last. Each clue has an answer, because the answer was in the grid before the clue existed. A setter who wrote 30 clues first and then tried to fit answers into the grid would be left with clues that no word of the right length can satisfy. The filled grid is the chain of tool calls built first, and the clues are the questions written afterwards. The setter with unfillable clues is the older method, which wrote the question first and threw away the examples it could not answer. The match ends here: a setter fills the grid in one sitting, while ToolGrad builds its chain one call at a time, trying tools and holding on to the one that worked.
●●●

Analogy

ToolGrad is Google's reverse-order way of making tool-calling practice for an AI: build the chain of tool calls, then write the question to suit it. Putting together a kids' treasure hunt is the same idea. You hide the prize, then walk back through the house writing a clue for each spot you just left. Every clue leads somewhere, because the hiding places came first. Do it the other way, scribble 8 clues at the table, then go looking for spots to match them, and you end up wandering the house with a clue about something that ticks and nothing that ticks. The hidden route is the tool chain built first, and the clue written on the walk back is the question written afterwards. The parent hunting for a spot to suit a clue is the old method, which binned the examples it couldn't answer. The kids can still come up empty, though: ToolGrad promises the question has an answer, not that the model will find it. Where it breaks: a parent picks hiding spots by looking around, while ToolGrad picks each step by running the tools and keeping the one that worked. 😎

Unfamiliar concept? A real-world example makes it click β€” fresh analogies on tap.

AI explanations may contain errors · Not professional advice

Formal definition β€” The same term, explained the usual way

ToolGrad is a dataset-generation framework from Google Research (Zhou et al., ACL 2026 Findings) for synthesising tool-use training data for large language models. It inverts the query-first paradigm of ToolBench and ToolACE, in which an instruction is generated and a depth-first search (DFS) agent then attempts to find a satisfying API workflow. ToolGrad instead constructs a validated workflow first, through an iterative loop (API proposer, parallel executors, selector and LLM updater) guided by textual gradients in the manner of TextGrad, and then synthesises the matching user query and response. Against the DFS baseline on the ToolBench API pool it reports a 99.8% pass rate versus 63.8%, and 3.4 ground-truth tool uses per sample versus 2.1. ToolGrad-500, generated with gemini-2.5-flash-lite, was used to fine-tune Gemma 3 models; the 12B variant scored 83.1 overall on the Berkeley Function Calling Leaderboard (BFCL), against 83.2 for gemini-2.5-pro at publication.

Want Clicked to explain terms like “ToolGrad” directly in your browser β€” including on PDFs?

Add to Chrome β€” Free

50 free Explanations · No credit card required