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

With readOnlyHint already declared, the description adds real value beyond annotations: the JSON:API pagination model (links.next/links.prev), the response envelope shape, and an explicit PII caveat. It omits auth/permission requirements and result-size limits, so it is strong but not exhaustive.

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?

Three tight sentences, front-loaded with purpose before pagination detail and the return-shape/PII note. Every clause carries distinct information with no 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?

For a read-only list tool with no output schema, the description covers purpose, pagination cursor mechanics, response envelope, and the PII caution, which is nearly everything an agent needs. Auth scope and default page size are not addressed, but the essentials are present.

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%, so all three parameters are already documented in the schema, including the cursor-to-links mapping. The description restates that mapping but adds no new syntax or constraints, 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 and resource ('List reports') and clarifies the resource with concrete examples (watchlist, adverse-media, business lookups), which meaningfully distinguishes it from persona_get_report. It does not, however, explicitly name a sibling or contrast singular vs. list semantics, so it stops short of full sibling differentiation.

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 implied by the resource description and the pagination note, so an agent can infer this is a browse/paginate operation. There is no explicit when-to-use vs. an alternative (e.g., 'use persona_get_report when you already have an id'), nor any exclusions.

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