4 thoughts filed under this tag.
A tool response that says only “something went wrong” leaves the next action to guesswork. Return a contained error that distinguishes useful recovery cases. For an order lookup, separate “not found,” “not authorized”…
A retrieved document can contain instructions that have nothing to do with the user's task. Its presence in a tool response does not give it authority. Use a synthetic search result that contains both a relevant fact…
“Prepare a refund” and “issue a refund” are different operations. Your tool interface should make that distinction visible. In a practice workflow, let the model propose the order, amount and reason. Have application…
A model's tool call is a request for your application to act. Validate that request before passing it to a database or service. For a synthetic order lookup, require an order identifier with the shape your system…
Learn
Save your progress with a free account.
Checking sign-in…
Cookie duty
The one he did not eat is a measurement cookie. Say yes and the site loads Google Analytics (GA4), which stores an identifier in your browser and lets us count which lessons get read.
Change your mind any time with Privacy choices in the footer. Read the Privacy Policy
Optional · newsletter
That is saved and settled. Separately, and this is marketing rather than measurement: Rod writes a weekly email — one lesson, one field note — sent through Kit. It has nothing to do with cookies, and skipping it costs you nothing.
We will send a confirmation email. Click the link in it and the next lesson finds you.
