Create a payment link

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

Adds substantial context beyond the annotations: it discloses that no money moves server-side and settlement is on-chain to `destination`, that the network is determined by the API key and dv_ keys are test networks with no real funds, and that reusing a memo is refused. These are operational facts the annotations (readOnlyHint=false, openWorldHint=true) cannot convey. The memo-based idempotency note sits alongside idempotentHint=false but is a caller-supplied key rather than a contradiction of server-side idempotency.

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 identity in the first clause and then packs conditional rules efficiently; nearly every sentence carries decision-relevant information. It is dense for a single paragraph, and the chain-standard parenthetical could be trimmed, but there is no filler.

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 compensates by naming the return fields an agent must act on (`checkoutUrl`, `paymentUri`, optional QR) and by describing the full lifecycle through to settlement. For a 9-parameter mutation on an open-world payment rail, that is complete enough to invoke correctly.

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 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: the Monad exception to omitting `amount`, and the native-coin default when `asset_code` is omitted. It stops short of explaining `memo`, `checkout_theme` or `include_qr` behavior, which remain schema-only.

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 and resource ('Create a payment request... a payment link') and immediately disambiguates by naming the per-chain standards it produces (SEP-7, Solana Pay, EIP-681) plus the QR code and checkout page artifacts. An agent can tell this apart from the read-side siblings get_payment/list_payments 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?

Gives explicit conditional guidance: omit `amount` to let the payer choose (except Monad), omit `asset_code` to charge the native coin, then send `checkoutUrl`/`paymentUri` and poll with get_payment. It names the follow-up sibling tool and the condition that selects it, leaving nothing to inference.

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