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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the description's real contribution is paging behavior: it explains that members are paged because a cluster can hold hundreds, and that the contrasting verified success appears only 'when one exists'. That is genuine behavioral context beyond the annotations, though it says nothing about ordering, permissions, or error modes.

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 sentences, both load-bearing. The return contents lead, and the paging rationale is placed last as the consequence rather than mixed into the enumeration. No filler or repetition of the title.

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?

No output schema exists, so the description carries the full burden of describing the return shape, and it does so thoroughly for a read-only detail endpoint — enumerating each section of the case. Minor gaps remain (ordering of decision history, whether members are sorted) but nothing an agent needs to call it correctly is 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 coverage is 100%, so every parameter (clusterId, customerId, memberLimit, including the superadmin-only constraint and the default/max on memberLimit) is documented in the schema itself. The description only indirectly motivates memberLimit via the paging sentence, adding no syntax or format detail beyond what the schema already provides — baseline 3.

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?

The description names the resource precisely — a single cluster's review case — and enumerates the contents (representative candidate, finding, evidence, proposed training target, verification, contrasting success, decision history, member page). An agent knows it retrieves the detail view for one cluster. It never states a verb or contrasts itself against near-siblings like get_review_queue or get_adjudication_queue, so differentiation is left to inference.

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 only implied: 'One cluster's review case' signals this is the per-cluster drill-down reached from a queue, and the schema notes clusterId comes from get_adjudication_queue or get_dataset. There is no explicit when-to-use, no exclusion, and no named alternative, so the routing decision is left for the agent to reconstruct from siblings.

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