MCP Dev MCP

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

The description adds context beyond annotations: it mentions the tool's response content and includes an example, which helps clarify behavior. Annotations indicate destructiveHint=true and openWorldHint=true, but the description doesn't contradict these; it supports them by describing execution with arguments. However, it doesn't detail potential side effects or error handling, leaving some gaps.

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 well-structured with clear sections (purpose, usage, args, returns, examples) and is front-loaded with the main purpose. It's concise overall, but the 'Args' section slightly duplicates schema information, though it's useful for quick reference. Every sentence adds value, such as the example clarifying practical use.

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 complexity (5 parameters, destructive operation, no output schema), the description is fairly complete: it explains the purpose, parameters, returns, and includes an example. However, it lacks details on error cases, response formats, or how to handle different transport types, which could be important for a tool with openWorldHint=true and destructiveHint=true.

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 the schema fully documents all parameters. The description lists parameters in the 'Args' section but doesn't add significant meaning beyond the schema, such as explaining interactions between parameters (e.g., how transport relates to target). It provides an example that illustrates usage, but this is more about guidelines than parameter semantics.

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 tool's purpose: 'Execute a tool on a target MCP server' and 'invoke a specific tool on the target server with provided arguments.' It uses specific verbs ('execute', 'invoke') and identifies the resource ('target MCP server'), distinguishing it from sibling tools that list or read rather than execute.

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 by stating it's for executing tools on MCP servers, but it doesn't explicitly guide when to use this versus alternatives like the sibling tools (e.g., list_tools or read_resource). There's no mention of prerequisites, such as needing to know the tool name from list_tools, or exclusions for specific scenarios.

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