Register MCP Server

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

Annotations indicate write-only and non-destructive behavior. Description adds transport support context but omits details like immediate monitoring start, authentication needs, or side effects.

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?

Single sentence that is front-loaded with the main action and resource, no wasted words.

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?

With 8 parameters, no output schema, and sibling management tools, the description is too minimal. It does not explain return value, error conditions, or how registration affects monitoring.

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 descriptions cover 88% of parameters; the description adds value by explaining the 'type' parameter enum values (http, sse, stdio) and their meanings.

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?

The description clearly states the action ('Register') and the resource ('an MCP server to monitor'), and distinguishes from sibling tools like list_servers and unregister_server by noting supported transports.

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?

The description implies usage for registering new servers but lacks explicit guidance on prerequisites, when to use vs alternatives like register_azure_pipelines, or when not to use.

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