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

The description adds meaningful behavior beyond the read-only/idempotent annotations: it discloses that the tool makes exactly 3 requests with 6-second timeouts, does not store the URL, and describes the shape of findings ('names the tool and says what breaks'). The annotation set already covers safety, so the extra behavioral detail earns a strong score without contradicting anything.

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 dense and contains mostly necessary information, but it is a single long run-on paragraph. The extensive fault checklist is valuable yet hard to scan; front-loading the tool's core action would have improved structure. Still, no sentence is filler.

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 that there is no output schema, the description compensates well by specifying what the report contains, the sequence of calls, the timeout, and an example. It could go slightly further by stating the exact response shape or error behavior, but the missing pieces are minor for this tool's intended use.

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%, so the schema already documents the url parameter well. The description adds value with a concrete example URL, the built-in fixture notation ({} for 'fixture://mcp-endpoint-lint/demo'), and server restrictions (refuses own publisher, IP literals, private names), going beyond the bare schema 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?

The description states a specific job: validate every tool returned by tools/list and report schema faults. It enumerates exact fault categories (missing description, invalid inputSchema, JSON-Schema violations, naming collisions), which makes the tool's purpose unambiguous and distinguishes it from sibling report tools like handshake_report or discovery_report.

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 the tool is used for endpoint tool-schema auditing and even gives an invocation example, but it never explicitly says when to choose this tool over siblings or when not to use it. The 'FIRST CALL, needs nothing' phrasing hints at sequencing but is ambiguous about whether it is a prerequisite or internal behavior.

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