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

Annotations already declare destructiveHint=true, so the agent knows this mutates state. The description does add genuinely useful context beyond that ('moves real money back to the customer'), flagging real financial consequence. However, it omits whether the refund is reversible, what authorization is required, and any rate/limit constraints, so it only partially enriches the annotated profile.

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 short, front-loaded sentences with zero filler; the core action and its partial-refund scope come first, and the risk warning follows. Nothing wastes the agent's budget.

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?

All five parameters are documented in the schema and the destructive nature is covered, so the definition is nearly sufficient. The remaining gap is behavioral: nothing about irreversibility or the consequences of revoke_benefits, which matters for a money-moving tool with no output schema.

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 all five parameters are already documented, including the amount-omission behavior and the revoke_benefits default. The description's 'in full or in part' merely restates what the schema already says for amount, adding no syntax or edge-case detail.

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 ('Refund an order') and adds scope ('in full or in part'), which cleanly separates it from the read-only sibling polar_list_refunds. It never names a sibling explicitly, so it stops short of the top band, but the purpose is unambiguous.

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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative tool. The closest thing to guidance is the caution that it moves real money, which warns about severity rather than helping the agent choose this tool over others.

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