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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds value the annotations cannot: irreversibility ('cannot be undone') and an entitlement gate ('Part of Premium'). It still doesn't say what happens on partial failure within a batch.

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, front-loaded with the action, then the gating condition, then the safety warning. No filler; every clause carries 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?

An output schema exists so return values need no explanation, and the description covers irreversibility, Premium gating, and pre-confirmation. The remaining gaps are batch-size limits and partial-failure behavior, which are minor but non-trivial for a bulk destructive operation.

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?

There is one parameter (ids) at 0% schema description coverage, and the description never explains it, nor mentions the 1–100 batch limit encoded in maxItems/minItems. The meaning is only weakly inferable from 'several waiting supporters', leaving the agent to guess at ID semantics and bounds.

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 (reject), resource (waiting supporters), and batch scope (several at once), which cleanly separates it from the singular reject_support and from bulk_approve_supports. An agent can select it without opening the 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?

Adds two real usage conditions: the tool is Premium-gated, and the list should be confirmed with the creator beforehand. It stops short of explicitly naming reject_support as the single-item alternative, so the when-to-use-vs-sibling routing is implied rather than stated.

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