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

Annotations only give the generic readOnly=false/destructive=false/openWorld=true profile; the description goes well beyond by disclosing the MPP/x402 payment handshake, the idempotent retry expectation after a challenge, the checkout_url/status_url fallback, and the warning not to recreate the order. That is exactly the operational context an agent needs for a payment-mutating call.

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 core purpose is front-loaded in the first clause and every sentence carries routing or constraint information. It is dense and runs long as a single block, but there is little genuine padding.

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 29-parameter, nested, open-world payment tool with an output schema, the description covers the critical decision logic (payment path selection, bulk exclusivity, fallback flow). Remaining gaps are field-level details that the schema already documents, so it is nearly complete but not exhaustive.

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 38% across 29 parameters, so the description carries a real burden. It clarifies the bulk branch (exactly one of csv_content/recipients, content_mode semantics, template pairing) and the payment params, but leaves many top-level fields (mail_class, certified, postcard_size, sender/recipient address options, letter render/signature) to the schema, so it only partially compensates.

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 pair (create/pay) and enumerates the exact resources: single PDF, letter, workflow-form order, or bulk letter campaign. It distinguishes itself from siblings by routing to draft tools + complete_checkout and to postalform.pay_order, so an agent can place it without opening a 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?

It states explicit when/when-not branches: bulk MPP orders may use postalform.pay_order after fetching the challenge; SPT-capable single-recipient clients should use a draft tool then complete_checkout; walletless clients must present checkout_url and poll status_url. It even forbids an anti-pattern ('never recreate the order to change payment paths').

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