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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond annotations by detailing what the report validates (tool definitions, schema quality, naming conventions, documentation completeness), giving insight into the tool's functionality rather than just its side effects.

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 three concise sentences: purpose, validation scope, and usage instruction. No redundant phrasing or unnecessary details, earning a top score for structure.

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?

With a strong output schema present and comprehensive annotations, the description sufficiently conveys the tool's purpose and usage. It omits mention of the `strict` parameter, but the schema covers that. The description is complete for a read-only report generator, though a brief note on output format could make it slightly richer.

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 input schema has 100% description coverage for both parameters, so the schema already defines their meaning. The description only reinforces that `manifest` is the server manifest JSON ('Paste the server manifest JSON'), and does not add extra semantics for `strict`. Therefore a baseline score of 3 is appropriate.

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 ('Generate') and a distinct resource ('health check report for an MCP server's tool manifest'), enumerating the validation dimensions (tool definitions, schema quality, naming conventions, documentation completeness). This clearly distinguishes it from sibling tools like mcp_schema_lint or mcp_server_evaluate, which focus on other aspects.

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 provides a clear usage context by instructing the user to 'Paste the server manifest JSON to audit', implying when to use it (i.e., to audit manifest health). However, it does not explicitly mention alternatives or when not to use the tool, so it stops short of full exclusion guidance.

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