Restart MCP Server

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

Annotations provide destructiveHint=true, readOnlyHint=false, idempotentHint=false. Description adds value: explains termination of Proton Bridge, graceful shutdown, spawning fresh process, and autoStartBridge behavior. No contradictions.

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?

Two sentences, front-loaded with purpose. Every sentence adds new behavioral information. No fluff.

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?

For a simple restart tool with good annotations and existing output schema, description covers all key behaviors: process, shutdown, restart, conditional bridge relaunch. Complete.

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?

Single parameter 'account_id' with 100% schema description coverage. Tool description does not add beyond schema, but schema already clarifies it is optional and for routing. Baseline 3 applies.

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?

Identifies specific verb 'Restart' and resource 'MCP server'. Differentiates from siblings like 'shutdown_server' and 'start_bridge' by detailing the full process (terminate Proton Bridge, graceful shutdown, spawn fresh process). No tautology.

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?

Implied usage: when the server needs restarting. Does not explicitly state when not to use or compare to alternatives like 'shutdown_server' or 'start_bridge'. Lacks exclusion criteria.

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