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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so safety is well covered. The description adds nothing about pagination behavior (page/limit exist in the schema), what happens when a list is still processing, or result ordering — modest added value on top of the annotations.

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 the resource scope front-loaded and no filler. It is efficient, though the terseness borders on under-specification given five parameters and paginated output.

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?

For a paginated read-only listing with five parameters, no output schema, and 60% schema coverage, an agent still lacks guidance on pagination defaults/limits, result ordering, and whether filtering by status=processing returns empty. The description covers the core purpose but not enough of the operational detail.

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 60%: id, page, and limit are documented in the schema, while result and status are bare enums with no inline descriptions. The description mentions filtering by result/status but does not clarify the semantic difference between the two or their relationship, so it only partially compensates for the coverage gap. 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?

The description names a specific verb and resource ("Return per-address results of a verification list"), which clearly separates it from get-verification-list (list metadata) and list-verification-lists. It does not explicitly name those siblings, so an agent must infer the distinction, but the scope statement is unambiguous.

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?

"Optionally by status or result" implies the filter use case but never states when to call this versus get-verification-list or list-verification-lists, nor any preconditions (e.g., the list must be completed before results exist). Usage is inferable rather than stated.

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