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

Annotations only cover readOnlyHint, so the description carries the rest of the burden and does well: it discloses the response envelope (JSON:API { data, links }), warns that returned objects contain PII, and explains the cursor pagination mechanism. It stops short of stating rate limits, default page size, or result caps.

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 the definition of a case and ending with the underlying REST endpoint. Slightly dense with the filter enumeration, but no sentence is wasted.

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 compensates by describing the return envelope, the PII sensitivity, and the cursor semantics, plus the REST path. For a 9-param filtering list tool this is nearly complete; only pagination defaults and result limits are missing.

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 nine parameters are already documented, giving a baseline of 3. The description's main added value is linking the page_after/page_before params to the response's links.next/links.prev cursors, but the rest of the filter list simply restates the schema.

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 cases') and then defines what a case actually is ('manual-review workflow items grouping inquiries/reports for an analyst to adjudicate'), which is the key disambiguator against siblings like persona_list_inquiries and persona_list_reports. An agent can tell what this returns without opening the schema.

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 frames the tool as a filtered collection read by enumerating the optional filters, which implies when to use it. However, it never contrasts with alternatives (e.g. persona_get_case for a single case, or the sibling list tools) or states when not to use it, so guidance is implied rather than explicit.

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