Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare non-readonly, openWorld, non-idempotent, non-destructive, but the description adds material context the annotations cannot: the spec is fetched over the network, tools are stored UNEXPOSED, and nothing is callable until a human publishes. It stops short of warning that repeat calls create additional draft servers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then a short rationale paragraph, then the return summary and the when-to-use line. The 'that is deliberate' sentence is slightly editorial but carries real behavioral intent, so the length is defensible.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description states exactly what comes back (server id, proposed tools with HTTP methods, console link), which is what an agent needs to proceed. Combined with the draft-state caveat, nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters (name, source_url) are already documented with format and constraints (public HTTPS, no credentials). The description restates the public-URL requirement without adding syntax beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Turn ... into) and resource (a DRAFT MCP server from an OpenAPI spec) and explicitly scopes the outcome as a non-published draft. An agent can distinguish this from get_server/list_my_servers/reintrospect_server purely from the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Ends with explicit when-to-use guidance ('Use when someone wants to give an agent access to an API they have a spec for') and clarifies a key exclusion — this tool cannot publish. It does not name a sibling alternative, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.