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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description goes well beyond them: irreversibility ('cannot be undone'), immediate deletion of the voice recording, the record being cleared a week later, and the absence of any page notification or supporter message. That is concrete, actionable side-effect disclosure.

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, zero filler, and correctly front-loaded: the usage condition comes first, followed by the irreversibility warning and the side-effect timeline.

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 not be described. Given the tool is a simple destructive single-record operation, the description covers trigger, reversibility, deletion timing, and external visibility completely.

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 0% for the single 'id' parameter, so the description has to carry the burden. It implies the id identifies one supporter (framing the operation as single-target versus bulk), but never states the id's format or which entity it indexes, leaving real ambiguity.

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) and resource (one supporter), plus the exact trigger condition (payment not found in bank). The 'one supporter' scope cleanly separates it from sibling bulk_reject_supports, and the reject-vs-approve polarity distinguishes it from approve_support.

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 clear when-to-use condition: reject when the creator has verified the bank and the payment is absent. It does not explicitly name alternatives such as approve_support or bulk_reject_supports, but the single-supporter versus bulk distinction is implied by 'one supporter'.

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