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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the probe mechanism (initialize and tools/list), explicitly promises no tool is ever called, describes the 30-day change signal and the rug-pull rationale, notes the registry coverage limit, that results are signed, and the exact per-call price and payment rails. This is the kind of operational detail an agent needs before invoking a paid check.

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?

Front-loads the usage instruction before the feature list, which is the right ordering. The middle sentence is a dense comma-list but every clause maps to a real output signal; the price/payment sentence is necessary context for a paid x402 tool.

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?

No output schema exists, so the description enumerates what comes back (uptime, connect time, sign-in mode, protocol version, tool count, change history, domain age, grade with reasons) and covers scope, cost, and safety constraints. An agent has enough to decide and call correctly.

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 carries the burden and does so reasonably: "by registry name or URL" maps the two bare parameters to the registry-name and URL lookup modes and signals they are alternative selectors. It does not state precedence if both are supplied or whether either alone suffices, leaving a small gap.

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 (independent checks) on a specific resource (a remote MCP server), and enumerates exactly what is checked: uptime, connect time, sign-in mode, protocol version, tool count, tool-definition changes, domain age, grade. It does not, however, distinguish itself from likely-overlapping siblings such as annalist_verify_mcp or mcp_top, so an agent cannot route between them from text alone.

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?

"Use before connecting a remote MCP server" gives an explicit trigger condition, and "Covers remote servers in the Official MCP Registry" gives a clear scope boundary that implicitly excludes non-registry servers. It stops short of naming an alternative tool or stating when NOT to use this one.

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