mcp_servers_restart

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the operation, not side effects like connection interruption, state reset, or configuration reapplication. The agent cannot anticipate consequences of calling this tool.

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?

The description is a single short sentence, front-loaded with the verb, with no wasted words. It is less complete than ideal, but for a one-parameter tool this brevity is acceptable; however, it could have included usage context without becoming wordy.

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?

Given the simplicity (one parameter, no output schema) and the presence of many sibling MCP server tools, the description should at least mention when restart is appropriate or what happens during a restart. It only states the action, leaving the agent without enough context to decide or anticipate outcome.

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 coverage is 100% (one parameter, 'name', with a description). The tool description adds no extra meaning beyond the schema; it merely restates the operation. This matches the baseline of 3 when the schema already documents the parameter.

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 'Restart an MCP server' uses a specific verb (restart) and a clear resource (MCP server), making the core purpose clear. It is distinct from sibling tools like start/stop, but it does not explicitly differentiate restart from reload, so it falls short of a perfect 5.

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 gives no guidance on when to use restart versus alternatives such as mcp_servers_reload or mcp_servers_start. There is no mention of prerequisites, effects, or situations where a restart is preferred, leaving the agent to infer usage without support.

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