A quiet shift is happening in developer experience: Your API docs are not only for humans anymore. They are for agents. Agents read schemas, tool descriptions, OpenAPI specs, MCP manifests, examples, error messages, and logs. They decide which function to call, what arguments to pass, how to recover from failures, and whether to retry. That means ambiguous API design is no longer just annoying. It directly reduces agent reliability. Agents Are Silent API Users Human developers complain in issues, Discord, Slack, Stack Overflow, or support tickets. Agents usually do not. They fail in quieter ways: choose the wrong tool pass subtly invalid arguments retry the same bad call hallucinate missing enum values ignore a useful endpoint give up and answer with incomplete context If you only monitor HTTP status codes, you miss most of the story. What Makes An API Agent-Ready? 1. Tool Names Should Be Boring Agents do better with literal names.…