MCP server.json Validator & Registry-Ready Skeleton Generator

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds valuable behavioral context: it runs client-side, zero PII, zero network, and inputs are applied via the AIN Bridge. This goes beyond annotations without contradiction.

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 a clear front-load: first sentence states core functionality, second sentence gives usage context and technical details. No wasted words; every sentence serves a purpose.

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?

The description explains inputs, outputs (findings, score, skeleton), and interaction model (widget, AIN Bridge, client-side). Without an output schema, it covers the return values adequately. Minor gap: no detail on findings format, but overall sufficient.

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?

The single parameter 'inputs' has 100% schema description coverage, explaining it is a map of tool input element IDs to values applied via AIN Bridge prefill. The tool description reinforces the AIN Bridge detail, adding value beyond the schema.

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 validates an MCP server.json against a specific schema (2025-12-11) and registry rules, and returns findings, a score, and an optional skeleton. It distinguishes itself from sibling tools like 'lint_mcp_tool_definition' and 'score_mcp_readiness' by targeting server.json validation for registry publishing.

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 explicitly says 'Use when a developer wants to check a server.json before publishing to the MCP Registry', providing clear context. However, it does not mention alternatives or when not to use this tool, which would improve guidance.

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