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

With no annotations, the description carries the full load and does so well: read-only scope limited to initialize and tools/list, cost and payment mechanism (x402, USDC on Base), the failure shape (isError with a 402 object in structuredContent), signing and public witnessing of the result, and an explicit statement of what was and was 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?

Front-loads the value proposition, then the mechanics, with no filler sentences. Minor redundancy between 'Signed report, logged in a public witnessed log' and the closing 'Result is signed by neo and logged.'

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?

Covers the essentials an agent needs for a paid, no-annotation, no-output-schema tool: scope, cost, payment handshake, and provenance of the result. The main gap is parameter meaning, which leaves the caller guessing what to put in previous_fingerprint.

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% and neither parameter is named or explained. The mention of fingerprinting implicitly hints at previous_fingerprint for change detection, but the link is never made, and 'url' (the target MCP server endpoint) is left entirely to inference.

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 concrete verb and resource plus the specific checks performed (hidden instructions, tool shadowing, annotation mismatches, transport faults, per-tool fingerprint). It does not, however, distinguish itself from plausible siblings like neo_inspect_mcp, verify_mcp_endpoint, or paid_injection_scan, which an agent would need to choose between.

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?

'Know what an MCP server can do to your agent before connecting it' gives a clear usage moment (pre-connection vetting), and the payment instructions tell the agent exactly how to proceed (call without payment, read the 402, retry with _meta['x402/payment']). No explicit when-not or sibling routing is given.

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