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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavioral context: it performs live network requests, runs multiple test categories, and returns a PASS/FIX/BLOCK verdict with a numeric score. This goes beyond the annotations by clarifying the tool's side effect of contacting an external server.

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 two sentences with no filler. It front-loads the main purpose, then efficiently lists the test components in parentheses and the output format. Every sentence earns its place.

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?

The tool has moderate complexity and an output schema, so the description does not need to reiterate return values. It covers the main inputs and outputs, and the annotations cover safety characteristics. Missing minor context like potential network prerequisites or timeout behavior, but not critical for invocation.

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% for both parameters (url and test_tool_name), and the schema already provides clear descriptions including the default behavior for test_tool_name. The description adds no additional parameter-level detail beyond what the schema supplies, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Run a full compliance evaluation') and clearly identifies the resource ('a live MCP server URL'). It enumerates concrete checks (ping, manifest discovery, schema quality, JSON-RPC call, latency) that distinguish it from generic tools like mcp_server_health_check or mcp_schema_lint.

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 when to use the tool (for comprehensive MCP server evaluation) and the phrase 'full compliance evaluation' suggests it is more thorough than a lightweight health check. However, it does not explicitly name alternatives or state when not to use it, so usage guidance remains implicit rather than explicit.

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