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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the instrument is USDC and that the amount is bounded, but says nothing about whether funds are held, what happens at expiry, how idempotencyKey deduplicates, or what the caller receives back.

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?

A single front-loaded sentence with no filler; the defining scope ('bounded', 'one named participant agent') arrives immediately.

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 non-read-only tool with five required parameters, no output schema, and zero schema descriptions, one sentence is far too thin. An agent cannot tell how expiry, idempotency, or the wallet/agent identifiers should be populated from this definition alone.

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 0% across six parameters, so the description carries the full burden and largely fails: only buyerAgentId ('one named participant agent') and amountMinor ('bounded') get any gloss. sellerWalletId, idempotencyKey, expiresAt, and description are never explained, and the USDC minor-unit convention behind amountMinor is left implicit.

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 concrete verb and resource ('Create a bounded USDC request') plus the counterparty model ('payable by one named participant agent'). This clearly separates it from send_payment (push) and get_payment_request (read), though no sibling is named explicitly.

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?

There is no when-to-use guidance and no named alternative. An agent must infer from the word 'request' alone that this is a pull-style invoice rather than a transfer, and nothing says when to prefer it over send_payment, request_withdrawal, or execute_authorized_purchase.

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