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

With no annotations provided, the description carries the full disclosure burden and does it well: it enumerates the verification pipeline and explicitly states the safety boundary ('Never invokes remote tools or forwards credentials'). It omits failure behavior, rate limits, or what a failed check produces, which keeps it short of a 5.

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?

Three tight sentences with the cost/prerequisite fact front-loaded, followed by scope and then the safety boundary. Every clause carries information; nothing is restated from the name or title.

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 zero annotation coverage, no output schema, and two undocumented parameters, the description needs to do more than describe the check pipeline. It never explains mutual exclusivity of the inputs, what the verification response contains (pass/fail signals, latency reporting), or behavior on unreachable endpoints, leaving real gaps for an agent 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 0% and neither parameter is described in the schema, so the description must compensate. It does so only indirectly, mapping 'public MCP HTTPS endpoint' to url and 'official Registry server name' to registry_name, but never states that the two are mutually exclusive alternatives, that both default to empty strings, or what a valid registry name looks like.

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: read-only verification of a public MCP HTTPS endpoint or official Registry server name, and enumerates the exact checks performed (DNS/SSRF, TLS/HTTP, initialize, tools/list, latency, discovery metadata). This is far more concrete than a sibling like neo_inspect_mcp, though the description never explicitly distinguishes itself from that similarly named tool.

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 phrasing 'public MCP HTTPS endpoint or official Registry server name' implies the applicable input types, and 'Free, no API key' sets a practical precondition. However, there is no explicit when-to-use/when-not-to-use statement, no guidance on choosing between the url and registry_name inputs, and no routing advice relative to the overlapping neo_inspect_mcp sibling.

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