The model orders; your code cooks.

A model's output is only text: here a structured decision naming a tool and its arguments. It has no hands. Some ordinary program has to read that decision, find the matching function and call it. That is exactly why limits and validation live in your code. The analogy bends in one place: a diner cannot cook, but a model can write a wrong order, so check it.

Read it once, then a question tests whether the trick stuck.