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

Beyond the read-only/idempotent annotations, the description discloses the actual validation rules (name charset and length, camelCase and zero-parameter tools accepted, inputSchema must be object, required fields listed in properties), the strict documentation checks, the PASS/WARN/FAIL derivation, and the important caveat that a tools/list carries no server name so those checks are not scored. That is substantial behavioral disclosure an agent could not get from annotations.

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-loaded with the core purpose and the accepted input forms, then the rules, then the verdict semantics. Dense but nearly every clause carries information; the parenthetical spec rules are long, though they earn their place as they define the contract.

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?

An output schema exists, so return-value structure need not be re-explained; the description still supplies verdict meanings and the correct gating expression, plus the tools/list scoring caveat. That is complete for a two-parameter offline validator.

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 100% and the schema already enumerates the accepted manifest forms and the strict semantics (≥20 chars, parameter description and type), so the description largely restates the structured fields. The only marginal addition is emphasis that `strict` extends validation to documentation, which is already stated in the property description.

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 ('Check an MCP server's tool definitions') plus a key scope qualifier ('without contacting it'), which distinguishes it from live-server tools. It does not explicitly separate itself from the closest sibling, mcp_schema_lint, leaving some ambiguity for an agent choosing between the two.

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?

Gives concrete when-to-use conditions: a server not deployed yet, a stdio server, or a CI gate, and names the gating mechanism ('Gate on verdict or on checks[tool_quality].pass'). It stops short of naming alternatives or exclusions, so an agent must infer when the sibling lint tool is preferred.

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