Tagged “api design”
- Write API descriptions for a reader who never sees your guides
OpenAPI descriptions used to be read by developers with a tutorial open beside them. Now tooling copies them straight into agents' tool definitions, and the description is all the model gets. It has to say when to call an operation, when not to, and what happens next.
- A rate limit is a message, so write it for an agent to read
Agents meet rate limits as text in their context, often after the useful numbers have been stripped out. Here is how to keep the signal intact, from the HTTP response to the tool result to the task's own budget.