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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description goes beyond them by spelling out the shape of each returned record (stable evidence_id, source types including document/locator/ipfs uri/gateway url/ledger claim id, SHA-256, verification state, freshness timestamps), which is genuinely useful since there is no output schema. It omits pagination behavior despite exposing limit/offset.

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, no filler, and the resource statement is front-loaded ahead of the filtering sentence. The dense field enumeration in sentence one is long but each element carries information.

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 describing the returned record fields, and annotations carry the safety profile. However, for a 7-parameter listing tool it leaves pagination (limit/offset) and the kind/type filter semantics undocumented, which an agent needs to page and filter correctly.

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 only 29% and the description does not close the gap. It names the filter parameters and repeats the status enum values already in the schema, but adds no meaning for the undescribed 'kind' and 'type' parameters (and no distinction between them), and never mentions limit/offset, so pagination semantics are absent from both places.

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 names the resource precisely ('the evidence records behind an asset') and enumerates the returned fields, so an agent knows this is a listing/retrieval tool. It does not, however, distinguish itself from close siblings like ruthven_get_evidence or ruthven_get_proof, which is the only thing keeping it out of the top band.

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?

Usage is only implied: 'Filter by status..., type, kind, or a text query' tells the agent how to narrow results but never says when to pick this tool over ruthven_get_evidence, ruthven_get_proof, or ruthven_get_provenance. No exclusions, prerequisites, or alternative-routing guidance are given.

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