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

Annotations already indicate destructive and non-read-only behavior. The description adds meaningful context beyond the annotations by explaining that the buyer is refunded and the sale amount is reversed from the wallet, clarifying real-world consequences. It does not contradict the annotations.

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 two sentences with no redundancy. It front-loads the action and payoff, then adds the financial consequence, making it efficient and scannable for an agent.

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 simple one-parameter tool, the description plus annotations cover the core behavior, including the payment processor and effect on buyer and wallet. It could mention prerequisites or failure cases such as insufficient wallet balance or non-paid orders, but the description already restricts to 'paid order' and the tool is otherwise straightforward.

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?

The input schema already describes the single parameter 'id' as an Order UUID with 100% coverage, so the description does not need to add parameter-level detail. The description provides no extra meaning about the id beyond what the schema already states, matching the baseline for full schema coverage.

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 clearly states a specific verb ('refund'), resource ('paid order'), and payment processor ('via Paystack'), and it distinguishes this from related financial siblings like request_payout or list_orders by focusing on refunding an existing order. The title and description align without ambiguity.

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 phrase 'Refund a paid order' implies when this tool is appropriate, but it does not explicitly state conditions, exclusions, or alternatives among the many related payment/wallet tools. Usage context is mostly inferred rather than explicitly routed.

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