I require that APIs publish explicit tool definitions that describe each callable capability as a discrete tool an agent can select, with clear names, descriptions, and typed inputs and outputs. These definitions should be authored deliberately during design, not reverse-engineered from an endpoint list after the fact, because the quality of the description is what determines whether an agent picks the right tool for the job. I push for this at design time because an operation that is legible to a human is not automatically legible to a machine, and the difference between the two is a few careful sentences per tool. Every API meant for automated consumers must treat its tool definitions as a contract, versioned and reviewed like any other interface.
Tool Definitions Provided
Strategies
APIs Are Legible to Automated Consumers
I want our APIs to be legible to the automated consumers reading them, not just to the humans who wrote them. That means operations that describe themselves clearly, tool definitions that spell out...
APIs Expose an MCP Server
I want our APIs to meet agents where they already are by exposing a Model Context Protocol server that turns our operations into tools an agent can pick up and use without a custom integration for ...
Experiences
Agent Experience
Agent experience is developer experience for machines. As AI agents become first-class consumers of APIs, the experience they have discovering, understanding, authenticating, and calling an API mat...
Automation
Automating business operations is a primary driver for adopting and governing APIs, enabling organizations to achieve the scale, speed, and quality needed to remain competitive in global markets. A...
Lifecycle
design_services Design Design
Design is where the human experience of an API is won or lost. I work design-first, shaping the paths, schema, errors, and naming in the contract before development begins, so that consistency is b...
