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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: reviewProgress is computed over every cluster while only the rows are paged, which prevents a caller from misreading paginated results as a scoped aggregate.

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 sentences, front-loaded with the primary return payload, then exclusions/alternatives, then the paging caveat. Dense but every clause carries information; slight verbosity in listing four member-resolution states inline.

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 carries the return-shape burden and does so: it lists the cluster fields, names the excluded candidates, and explains paging vs aggregate scope. It does not mention the superadmin-only nature of customerId or auth requirements, a minor gap the schema partially covers.

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 is 3 and the schema already documents limit/offset/datasetId/customerId/reviewState. The description still adds meaning by clarifying that limit/offset page only cluster rows and do not bound the reviewProgress aggregate, which the schema alone does not convey.

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+resource (get one dataset's cluster roll-up and review progress) and enumerates the returned fields: each behavior cluster's review state, the decision in force, and member resolution. It explicitly distinguishes itself from list_dataset_examples and get_review_case, so an agent can route without opening any 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?

Names alternatives with the condition that selects them: candidates are not returned here, so per-example admission goes to list_dataset_examples and single-cluster evidence goes to get_review_case. It lacks an explicit 'use this when' framing relative to the other review-queue siblings, but the routing guidance is concrete and actionable.

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