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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that results are grouped by category and that values feed `rejectionReason`; it says nothing about ordering, pagination, or how inactive/deprecated reasons are handled. Useful context, but thin beyond what annotations supply.

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, zero waste, with the core purpose front-loaded and the downstream-usage hint immediately after. Nothing could be cut without losing information.

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 parameters, no output schema, and complete annotations, the description covers what the tool returns at a high level (categories of reasons) and how to consume it. It is adequate, though a note on whether the list is static per organization or includes disabled reasons would close the remaining gap.

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?

Zero parameters, so the baseline is 4; the schema adds nothing to describe. The description goes slightly beyond by explaining the semantic role of the `value` field in the response and where it must be reused, which is meaningful guidance for a no-param tool.

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 the rejection reasons") plus its scope ("configured for the organization") and return shape ("grouped by category"). It doesn't name a sibling tool directly, but the follow-up sentence ties it to the rejection workflow, so an agent can place 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?

Gives a concrete usage rule: take a `value` from this list and pass it as `rejectionReason` when rejecting a candidate. There are no competing tools for this data, so the absence of explicit exclusions is a minor gap rather than a real ambiguity.

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