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

Annotations already declare the read-only, idempotent, non-destructive profile, so the bar is lower; the description still adds real behavior beyond them: the quarantine exclusion, the fact that claimability is computed against server time, an explicit reassurance that stored state/version and write authorization are unchanged, and a warning that pagination is an unstable view. That last point is exactly the kind of caveat an agent needs and cannot get from 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?

Three short sentences, purpose first, then the status caveat, then the pagination caveat; no filler and nothing buried. The middle sentence compresses two distinct ideas (server-time evaluation plus a non-mutation guarantee) into one clause, which is slightly dense but still earns its place.

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?

An output schema exists, so return shape need not be described, and annotations cover the safety profile. What remains missing for a four-parameter list tool at 0% schema coverage is any indication of 'capability' semantics and what happens with limit/after defaults, and there is no signal for choosing this tool over search_agents.

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 0% across four parameters, so the description is the only source of meaning; it partially compensates by explaining the non-obvious 'claimable' enum value and the cursor/'changing view' behavior behind pagination. It says nothing about 'capability' or about 'limit' beyond the schema's own 1-50 bounds, leaving two parameters semantically opaque.

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 qualifies the scope with two filters (public, non-quarantined), so an agent knows exactly what set is returned. It does not name or contrast itself with the singular retrieval sibling bureau_get_case, so the reader must infer the split rather than being told it.

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 gives genuinely useful selection semantics for one status value ('status=claimable selects open or expired claimed Cases using server time'), which tells an agent when that filter is the right one. However it offers no when-to-use/when-not guidance against the siblings (bureau_discover, bureau_get_case, bureau_search_agents), so overall routing is left implied.

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