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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing the financial impact (spends money, balance used first, payment method must be on file), the return contents, the refund window, the per-call confirmation default, and the API key requirement. Spending money is not contradicted by destructiveHint=false, so no contradiction.

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?

Front-loads the core action and cost implication in the first two sentences, then layers refund, confirmation, and auth notes. Slightly verbose with the 'Reaches other people' phrasing, but every sentence carries actionable information.

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 money-spending, irreversible-ish mutation with no output schema, it covers cost, payment prerequisites, return payload, refund path, and auth. Minor gap: no stated precondition that a rate must first be fetched via get_rates, but the schema and description imply it.

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 four parameters are already documented (rate_id from get_rates, extras, ship_date default today, insured_value_usd). The description adds only the conceptual 'buy from a rate' framing and no syntax or format detail beyond the schema, so 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?

States a specific verb+resource (buy one label) plus scope (from a rate), which cleanly distinguishes it from siblings like pirate-ship_buy_batch (buys a batch) and pirate-ship_get_rates (read-only). An agent can pick the right tool without opening any schema.

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?

Provides strong operational guidance: refund_label is named as the reversal path within 28 days, and the confirmation/key requirements are spelled out. It does not explicitly contrast buy_label against buy_batch or state the precondition of obtaining a rate_id, so it stops short of full when/when-not routing.

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