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

With no annotations, the description carries the full burden and does so credibly: it declares read-only behavior and three explicit negative guarantees ('never invokes remote tools, never forwards credentials, never affects commercial gates'), plus 'Free, no API key.' It omits rate limits, auth expectations, and failure/error behavior, so it stops 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 dense sentences, front-loaded with the most decision-relevant facts (free, no API key, read-only). Little waste, though undefined jargon ('MYCELIX', 'commercial gates') costs some clarity.

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?

A diagnostic tool with three undocumented parameters, no annotations, and no output schema needs the description to explain inputs and what 'classifies technical failures' actually returns. The description covers behavior and safety well but leaves parameter semantics and result shape entirely unaddressed.

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% for three parameters, so the description must compensate. It alludes to expected_capability ('compares the requested capability with declared tool metadata') and obliquely to registry_name, but says nothing about url, format expectations, or how the two endpoint-identifying params differ. Partial at best given the near-total schema 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+resource: a read-only MCP diagnostic that verifies endpoints, classifies technical failures, and optionally compares capability against tool metadata. An agent can understand the function without opening the schema. It does not, however, explicitly differentiate itself from the closely related sibling verify_mcp_endpoint (it only says it 'reuses' that verification), so it falls short of a 5.

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 its use case (diagnosing MCP endpoint/registry failures, free with no API key), which lets an agent infer when it applies. But it never states when to prefer it over siblings like verify_mcp_endpoint, neo_preflight, or neo_inspect_mcp, nor any exclusions or prerequisites.

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