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

Goes well beyond the annotations (readOnly/idempotent/non-destructive/closed-world) by disclosing that counts reflect an inspected sample rather than all production traffic, that saved findings are not auto-resolved after a fix, that lists may end early and require nextCursor, and that results may contain end-user PII requiring masking. These are real caveats an agent cannot infer from structured fields.

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, then filters, caveats, sibling routing, pagination and privacy guidance; every sentence adds distinct operational value. It is dense but not padded, running one sentence longer than strictly necessary.

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 an output schema present, return-value explanation is not needed, and the description still covers the operational essentials: scoping, freshness/resolution semantics, pagination continuation, and PII handling. Nothing an agent needs to call this correctly is missing.

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?

With only 50% schema coverage, the description compensates by mapping the filter surface ('Filter by server, tool or category') and by explaining pagination behavior ('Lists can end before the requested limit; follow nextCursor'). The required reason/user_intent/namespace_id parameters are covered by their own schema descriptions, so no significant gap remains.

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 and resource ('List saved, evidence-backed MCP improvement recommendations') plus ordering ('newest first'), and explicitly distinguishes itself from the sibling get_mcp_recommendation, which it names as the detail-view counterpart. An agent can route between the two without opening either schema.

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 clear usage context ('Filter by server, tool or category') and names the alternative verb explicitly: 'Use get_mcp_recommendation for the rationale, qualifications, concrete change and evidence.' No explicit when-not-to-use guidance relative to other MCP siblings such as get_mcp_overview, so it falls short of a full 5.

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