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

Annotations already declare readOnlyHint=true, so safety is covered by structured data. The description adds real value beyond that: it discloses the JSON:API envelope shape ({ data, links }), that returned objects contain PII, and that pagination must follow links.next/links.prev into page_after/page_before. It stops short of stating rate limits or result-scoping/permissions.

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 dense sentences, front-loaded with the resource definition before the filter/pagination mechanics. Every clause carries information, though the filter enumeration is a long mid-sentence list that mildly blurs the read.

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 9-parameter, zero-required list tool with no output schema, the description covers return shape, PII risk, and cursor-based pagination — the things an agent most needs. It omits default page_size behavior and whether results are scoped by account/permission context.

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 100%, so the baseline would be 3. The description rises above it by tying the pagination parameters to the response's links.next/links.prev cursors, explaining how to obtain a cursor rather than just what it does, and by grouping the filter set into a coherent list.

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 (List) and resource (cases), then defines what a case actually is — "manual-review workflow items grouping inquiries/reports for an analyst to adjudicate" — which is domain knowledge an agent cannot derive from the name. That definition also implicitly separates it from the persona_list_inquiries/reports siblings, since cases are the grouping layer over them.

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 description enumerates the available filters and cursor parameters, which implies the intended usage (narrow a case set, then page through it). However, it never says when to reach for this tool versus persona_get_case (single case lookup) or the other persona_list_* tools, and states no exclusions or prerequisites.

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