Refund Community Member Charge

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false. The description's 'changes community state' largely restates that, but 'requires confirm=true for the user-requested action' is genuinely useful added context about a guard condition. It omits reversibility, permission requirements, and rate limits.

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 compact sentences with no filler, and the state-changing/confirm constraint is front-loaded. It is efficient, though the opening restatement of the title is slightly redundant.

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 destructive, open-world, non-idempotent financial tool with a nested payload and multiple mutually exclusive body-input options, the description is thin. The schema and annotations carry most of the load, but the description never warns about irreversibility or the payload/payload_file exclusivity.

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 the schema already documents charge_id, amount, account, confirm, payload, payload_file, and reason_details. The description adds no syntax or format detail beyond what the schema provides, so the 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?

The description states a specific verb+resource (refund a Community Member Charge), making purpose unambiguous. However, the first sentence is essentially the title repeated verbatim, and there is no differentiation from sibling tools (e.g., cancel/resume subscription, list_charges).

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?

It discloses the confirm=true gating requirement and ties it to 'the user-requested action', which is a usage constraint. But it offers no when-to-use vs alternatives guidance, no prerequisites, and no exclusion cases (e.g., partial vs full refund conditions).

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