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

With no annotations provided, the description carries the full burden, and it does well: it discloses that the tool performs a real network handshake, checks live server endpoints, handles auth-protected servers, and provides scored results. It also mentions rate-limit expectations. It stops short of explaining any failure modes or side effects in more detail, but it is considerably more transparent than most.

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 longer than average but front-loaded and information-dense; each sentence adds purposeful context about behavior, use cases, or limits. The x402 payment and pricing details are somewhat promotional but still useful for high-volume usage guidance, so the length is justified.

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?

Despite having no output schema, the description comprehensively covers the returned score, letter grade, per-check breakdown fields, concrete fixes, auth-posture handling, and rate-limit expectations. Together with the single well-documented parameter, this makes the tool description complete enough for an agent to select and invoke it appropriately.

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?

The input schema already documents the only parameter (url) with 100% coverage, including format, scheme-assumption, and private/localhost rejection. The description adds no new parameter-specific detail beyond restating 'streamable HTTP,' 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 opens with a specific verb and resource: 'Run a free, live health, conformance and latency scan of any remote MCP server.' It distinguishes itself from siblings by detailing the concrete JSON-RPC handshake, the 0-100 score letter grade, and the per-check breakdown, and by giving exact use cases like debugging why an agent platform rejects a server.

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 clear when-to-use guidance: 'Use it before recommending, installing or listing an MCP server, or to debug why an agent platform rejects one.' It also addresses volume constraints with the free-tier self-limit and the pay-per-call alternative, but it does not explicitly name sibling alternatives or state when not to use this tool.

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