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

Annotations only declare readOnlyHint=true, so the description carries the rest — and it does add real value: the JSON:API { data:[...], links } return shape, the PII warning on returned objects, and the cursor-following pagination contract. It omits auth requirements and rate limits, but for a read-only list endpoint this is solid disclosure beyond the annotation.

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 tightly packed sentences with the core purpose front-loaded, then pagination, then return shape. The trailing REST endpoint note ('Persona REST: GET /reports') is oriented toward implementers rather than the agent choosing the tool, which is the only near-redundant element.

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 and only a readOnlyHint annotation, the description steps in to describe the return envelope, the PII sensitivity, and the pagination loop — enough for an agent to call and traverse results correctly. Missing only complementary detail such as ordering or filtering behavior.

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 already explains each cursor parameter ('return the page AFTER this record id (follow the links.next cursor)'). The description largely restates that links.next maps to page_after and links.prev to page_before, adding convenience but no new meaning, 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 immediately defines what a report is in this API (screening/monitoring results such as watchlist, adverse-media, or business lookups), which is knowledge the agent cannot infer from the name alone. It also pins the operation to the Persona REST surface (GET /reports), so it is distinguishable from the get_* siblings.

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?

The pagination instruction ('paginate via links.next cursor') gives operational guidance, which implies this is the bulk-retrieval tool. However, it never states when to use this versus persona_get_report (known ID) or the other list_* siblings, and gives no prerequisites or exclusions.

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