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

Goes well beyond the annotations: mailing happens immediately after payment, no cancellation or recall, the payment is the point of no return, the link expires in ~24 hours, and repeat calls with the same quote_id return the same letter or its current status. That last point corroborates idempotentHint=true rather than repeating it. Minor gap: it never states what the returned object contains beyond the link, and the irreversibility sits a bit awkwardly next to destructiveHint=false, though sending a new letter is not data destruction, so this is not a 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-loaded with the core action and the critical do-not-pay warning, then proceeds to consequences and edge cases. The x402 paragraph is long and only relevant to a subset of agents, but it is clearly demarcated and materially changes routing decisions, so it earns most of its space.

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?

With no output schema, the description carries the burden of the return value and does so (payment link, status after payment, expiry). For a mutation tool with open-world effects, the lifecycle, idempotency, and human-in-the-loop requirement are all covered.

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 coverage is only 50%, but the description compensates: it explains that quote_id acts as an idempotency key returning the same letter/link, and that webhook_url must be a public https URL notified on each status change. It does not spell out the qt_ prefix/format constraint, which the schema pattern already enforces.

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?

Opens with a specific verb and resource: 'Creates the letter for a quote and returns a payment link (Stripe Checkout)'. It is clearly distinguished from the siblings quote_letter (pre-payment quoting) and get_letter_status (polling), so an agent can route without opening the 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?

Explicitly states when to use it, what it must not be used for ('YOU CANNOT PAY' – hand the link to the human), the sibling to poll afterwards (get_letter_status), and a concrete alternative path (x402 via REST POST /v1/letters, including the 422 failure mode).

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