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

The annotations already establish that this is a non-read-only, non-destructive, non-open-world operation. The description adds that results are sent for review and a refund, but it does not explain claim lifecycle, whether review is synchronous or asynchronous, what idempotency guarantees apply, or what happens after submission.

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?

The description is a single sentence with no filler and is reasonably front-loaded. Its brevity contributes to the parameter and usage gaps, but it is not structurally wasteful.

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?

This is a mutation tool with four required parameters, no output schema, and no parameter descriptions in the schema. The one-sentence description does not provide enough context to call it correctly or to distinguish it from closely related siblings like report_wrong_result.

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%, and all four parameters are required, so the description must compensate for the missing parameter documentation. It does not explain reservation_id, unit_ids, reason, or idempotency_key; the phrase 'charged results' does not clarify what unit_ids represent or how reason should be supplied.

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 indicates an action around charged results that fail request conditions, leading to review and refund. However, it does not clearly distinguish this from the sibling tool report_wrong_result, whose title is identical to this tool's title, nor does it explain how the refund-claim resource relates to the existing get_capacity_refund_claim tool.

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 implies usage for charged results that do not meet request conditions, but gives no explicit when-to-use or when-not-to-use guidance. There is no mention of alternatives such as report_wrong_result, get_capacity_request, or get_capacity_refund_claim, which is a significant gap given the sibling overlap.

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