Tools API, in practice.

Define the input, action, and output before choosing an implementation. A tools API may wrap a narrow operation or participate in a larger workflow, but the caller still needs an understandable contract. This topic brings together the basic questions: what the action accepts, where it runs, which permissions it needs, and how failure is represented.

Use these articles to make a first design review concrete. Ask whether someone can distinguish a rejected request from an attempted action, whether a repeated call can repeat a side effect, and what evidence supports the reported result. Then follow the workflow links for the specific action you want to build. Review question: Could a new caller describe the accepted inputs, meaningful outcomes, permission boundary, and safe next step after an uncertain result?