execute_tool

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

With no annotations, the description carries full burden. It discloses permission validation and forwarding, but omits details like error handling, side effects, rate limits, or what constitutes a valid permission. It is adequate but not comprehensive.

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 extremely concise at three sentences, front-loaded with the core action, and contains no filler or redundant information. Each sentence adds value.

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 that output schema exists and parameters are well-described in schema, the description completes the picture by explaining the gateway validation and forwarding flow. It is nearly complete, though it could mention that args must match the downstream tool's inputSchema (already in schema) and that errors may come from the downstream server.

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%, so baseline is 3. The description adds context about the gateway role ('validates permissions then forwards'), but the parameter descriptions in the schema already explain each field sufficiently. No additional meaning beyond schema is provided.

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: 'Execute a tool on a downstream MCP server'. It specifies the resource (downstream MCP server) and distinguishes from sibling tools (list_servers, get_server_tools, get_gateway_status) which are about discovery or status, not execution.

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 that this tool should be used after listing servers and tools, but it does not explicitly state prerequisites or when not to use it. There is no guidance on alternatives or context, leaving the agent to infer usage from parameter names.

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