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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: widget rendering, inputs applied via the AIN Bridge prefill, client-side execution, zero PII, zero network. That is meaningfully non-obvious behavior for an agent to know. It does not detail rate limits or what happens on an invalid definition input.

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 purpose and outputs in sentence one, then usage, then execution model, then a pointer to describe_tool. Four sentences, each carrying distinct information, though the widget/AIN Bridge sentence is somewhat stacked with unexplained terms.

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?

For a single-parameter read-only validator with no output schema, the definition covers what it does, when to use it, and what it returns at a high level, and even redirects to describe_tool for the full output contract. What 'findings' contain and their severity structure is left entirely to that redirect.

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?

Only one parameter (`inputs`), and schema description coverage is 100%, so the schema already explains the ID-to-value map. The description adds a small amount by saying inputs are applied via AIN Bridge prefill, but nothing about expected keys or the manifest input_schema is expanded.

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 (validate) and resource (an MCP tool definition), plus the rule families checked (JSON Schema 2020-12, naming, output-schema, annotation) and the outputs (findings, conformance score, recommended annotation set). The 'tool definition' scope implicitly separates it from server-level siblings like lint_mcp_server_conformance, but no sibling is named explicitly.

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 a clear trigger: 'Use when a developer wants to check an MCP tool definition before publishing.' That is a concrete life-cycle moment rather than a vague gesture. It stops short of exclusions or naming an alternative (e.g. lint_mcp_server_conformance for server-wide checks, score_mcp_readiness for scoring).

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