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

Annotations already cover read-only/idempotent/non-destructive, so the safety profile is handled; the description adds real value beyond them by disclosing the shape of the return and its limits — notably that some checks could not run and that 'No warnings is NOT a safety guarantee.' That interpretive caveat is exactly the kind of disclosure an agent needs. Deducting one point because failure behavior (unknown identifier, partial resolution) isn't described.

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?

Two sentences, purpose front-loaded before the evidence list, and the caveat placed last where it lands as a warning. The enumeration is dense but every item names a distinct evidence category the caller will receive, so none of it 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?

With no output schema, the description usefully substitutes by naming the returned evidence categories, and annotations handle the safety profile. It's slightly incomplete in not covering bad/unresolvable identifiers, especially given a resolve_identifier sibling exists that hints at a preprocessing step the caller isn't told about.

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% and the single parameter's description already spells out the accepted forms (server name, catalog id, or GitHub repo URL). The description text adds nothing about the identifier, so baseline 3 applies — the schema carries all parameter meaning.

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 outcome: an evidence summary about an MCP server, and enumerates the evidence categories (publisher identity, provenance, vulnerabilities, install scripts, maintenance, warnings, skipped checks, recent changes). What's missing is sibling differentiation — several siblings (get_evidence, get_publisher, get_tool) sound like they return overlapping data, and the description never says this is the composite/pre-install rollup versus the granular getters.

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?

'before you install or connect it' gives an explicit trigger condition, which is clear decision context. It stops short of exclusions or alternatives — it never says when to prefer get_evidence or get_tool instead, or what to do if the identifier isn't recognized.

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