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

Annotations already declare readOnlyHint=true and idempotentHint=true, so no contradiction. The description adds 'Returns actionable warnings' and the list of lint checks, but it does not disclose edge cases, behavior on invalid input, or the exact structure of warnings, which the output schema may not fully convey.

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 one dense, front-loaded sentence that efficiently lists the tool's scope and output. Every phrase earns its place—no filler or repetition of schema content.

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?

Given the low complexity (one parameter), rich annotations, and presence of an output schema, the description is largely complete. It covers purpose, checks, and return value. It slightly lacks explicit context about preconditions or alternative tool disambiguation, but these are minor given the tool's simplicity.

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 100% for the single tool_definition parameter, so baseline is 3. The description repeats the parameter's purpose (linting that definition) but adds no extra semantic detail beyond the schema's 'object with name, description, inputSchema'.

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 uses a specific verb ('Lint') and resource ('MCP tool definition') and enumerates concrete aspects (naming conventions, description quality, schema completeness, required fields consistency, description length). This clearly distinguishes it from sibling tools like mcp_server_evaluate or validate_mcp_response.

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 usage: when you need to validate an MCP tool definition against best practices. However, it does not explicitly state when to prefer this over alternatives, nor does it mention exclusions or prerequisites, leaving some ambiguity.

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