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

With no annotations provided, the description carries the full burden. It explicitly states 'Read-only', 'Never invokes remote tools or forwards credentials', and lists the checks performed. This is strong transparency for safety, though it omits potential rate limits or auth requirements, which are minor for a read-only verifier.

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 the key safety trait ('Read-only') front-loaded. It packs many relevant details (checks, safety promises) without redundancy. Every word adds value, making it highly efficient.

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 the tool's simplicity (2 params, no output schema), the description covers the core purpose, safety, and checks. It is missing explicit parameter relationship (url vs registry_name) and potential error conditions, but these are reasonable omissions for a read-only verification tool.

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 0%, so the description must clarify parameters. It does partly, indicating 'url' is for a public HTTPS endpoint and 'registry_name' for an official server name. However, it does not specify if they are mutually exclusive, required vs optional, or format expectations, leaving ambiguity.

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 tool verifies public MCP endpoints or Registry servers, with a specific list of checks (DNS/SSRF, TLS, initialize, tools/list schema). It uses the verb 'verify' with a clear resource, but it does not explicitly distinguish from sibling tools like neo_inspect_mcp, so it lacks direct differentiation.

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 it (for verification of endpoints or Registry names) but provides no explicit guidance on when not to use it or which sibling tool to prefer. There is no mention of alternatives or exclusions, leaving the agent to infer usage context.

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