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

Goes well beyond the annotations by disclosing the exact wire behavior ('sends initialize and tools/list only — no tool is ever called'), privacy handling ('query strings are removed before anything is sent or stored'), scope limits ('public addresses only'), auth posture ('requires no API key'), and rate limiting. It also states the negative space: what is behind a login or in the server code is explicitly listed as not checked.

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?

Dense and front-loaded — the first sentence establishes purpose and scope before details follow. It is long, but nearly every clause adds a distinct behavioral fact; a slight trim of overlapping 'what is not checked' phrasing would sharpen it.

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?

For a one-parameter, read-only diagnostic tool with an output schema, the description covers everything an agent needs: purpose, preconditions, safety profile, and scope limitations. The return values are even summarized (status, KPIs, issues, actions, report link) despite the output schema making that optional.

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% and the single url parameter is fully documented in the schema, so the description adds no syntax or format meaning beyond it. The mention of query-string removal duplicates the schema note rather than extending it, so the baseline 3 is correct.

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?

States a specific verb and resource ('Check a remote MCP server from outside') and enumerates exactly what is checked (auth/OAuth metadata, world-acting tools, tool poisoning, CORS/Origin, HTTPS, annotations). No sibling tool (security_scan, http_security, owasp_check) targets MCP endpoints, so it is clearly distinguishable from the rest of the family.

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?

Gives a clear triggering context ('before connecting it to an agent') that tells the agent when this tool belongs in a workflow. It does not name an alternative sibling or state when not to use it, so it stops short of full routing guidance.

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