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

Annotations already declare the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the safety burden is covered. The description does add genuine content-level context beyond annotations by disclosing that results are trust-labelled — registry-run vs. PUBLISHER CLAIMED — and include signed attestations. It still omits anything about freshness, caching, or what happens when a capability has no benchmark data.

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?

A single dense sentence with no filler, and the most important information (what evidence is returned) is front-loaded. It is telegraphic to the point of being slightly clipped, but nothing is wasted.

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?

No output schema exists, so the description must carry the return-shape burden, and it does give a usable inventory of returned content types. However, for a tool in a crowded read-only evidence family it lacks guidance on selection versus siblings and on behavior when evidence is absent.

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%, and the schema itself documents the accepted id/URI/slug forms for the single capability parameter. The description adds no format, resolution, or error semantics beyond the schema, so the baseline 3 applies.

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 (get) and resource (benchmark evidence) and enumerates the actual content returned: registry-run benchmark summaries, publisher claims, and signed attestations. This is far from tautological, but it never distinguishes itself from closely related siblings like get_provenance, get_capability, or evaluate_capability.

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?

There is no when-to-use guidance, no conditions or prerequisites, and no mention of any alternative tool. With nine siblings in the family (get_capability, get_provenance, evaluate_capability, compare_capabilities), an agent gets no help deciding which evidence-retrieval tool to call.

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