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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is largely covered. The description adds the customer-confirmation precondition, but that is also encoded in the schema's `confirmed: {const: true}`, so the added behavioral value is modest.

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?

A single front-loaded sentence with no filler: the decision, its scope, and its precondition in one clause. Nothing to trim and nothing buried.

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 an irreversible, state-changing order decision with no output schema, and the description omits what happens after the choice, whether it can be undone, what 'eligible' means, or what the agent should report back. For a destructive tool that commits a refund or replacement, that is a notable shortfall.

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%, so the description must carry parameter meaning. It conveys the two valid `action` values (refund vs replace) and the confirmation requirement, but says nothing about where `orderId` comes from or what 'eligible' means operationally, leaving a gap for the third parameter.

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 names a specific verb ('Choose') and the concrete decision domain ('refund or replacement' for an order), which an agent can distinguish from neighbors like orders_request_cancellation or orders_confirm_delivery. It stops short of naming a sibling explicitly, so a 5 is not warranted.

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 gives a clear precondition: the order must be 'eligible' and the action may only be taken 'after explicit customer confirmation.' That is real when-to-use guidance, though it never names an alternative tool or states what to do when the order is not eligible.

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