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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context by specifying what items surface in the queue (undecided clusters, unverified training targets, unresolved members), which tells the agent what to expect from the call beyond the safety hints.

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?

Front-loaded with the resource definition, then the sibling exclusion, then the routing questions. It is appropriately sized and every sentence serves routing, though the trailing 'Answers:' clause slightly restates the purpose already stated.

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 read-only, 3-param, no-output-schema tool whose annotations carry the safety profile, the description covers purpose, contents, and sibling disambiguation adequately. Nothing essential to invoking it correctly is missing, though return shape or pagination behavior are left unstated.

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 limit, datasetId, and customerId are already fully documented in the schema (including the superadmin note on customerId). The description implies dataset scoping ('on this dataset') but adds no syntax or default details beyond the schema, so baseline 3 applies.

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?

Specific verb+resource (get_adjudication_queue) plus an enumeration of exactly what the queue contains: clusters with no decision in force, unverified training targets, and unresolved members. It explicitly distinguishes itself from the sibling get_review_queue, so an agent can tell them apart without opening either 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 the alternative it is not (get_review_queue = optimization PR queue) and states the questions it answers ('what needs adjudicating?', 'how much review is left?'), which routes the agent correctly. It gives clear positive usage and one exclusion, though it does not enumerate other sibling alternatives or broader when-not conditions.

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