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

Goes well beyond the annotations by disclosing hard caps (25.00 USDC per payout, 100.00 daily), the required X-Wever-Wallet-Proof bound to exact JSON arguments and API path, the paid URL pricing (0.10 USDC x402 on Base), the free-call allowance, and custody constraints (no private keys, manual wallet funding). The 'No money moves' claim is consistent with destructiveHint=true applying to the immutable record creation, and idempotentHint aligns with idempotency_key, 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?

The operation, caps, and auth are front-loaded effectively, but the back half drifts into tangential custody/legal boilerplate ('Ledger keys never reach the server', 'sweep and reclaim remain manual', 'Externally audited', 'Company-authored') that does not help an agent select or invoke the tool.

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 correctly states the return ('created with a signed receipt'), covers authorization, pricing, and caps, and points to /api/payout-contract for exact schemas. The only gap is that the 'usage' enum parameter is left unexplained.

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%, so the description carries the burden. It names all five required parameters and adds meaningful constraint context (the 25.00 USDC cap on amount_usdc), but leaves the 'usage' enum, the address pattern, the amount string format, and idempotency_key format entirely to the schema.

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 an immutable payout instruction') and enumerates the core fields (recipient, amount_usdc, idempotency_key, memo, rail_reference). It also distinguishes its lifecycle stage from the execute sibling by declaring 'No money moves', though it never names the alternative tools 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?

Usage is implied through 'immutable payout instruction' and 'No money moves', suggesting this is the first step before an actual disbursement, but there is no explicit when-to-use or when-to-prefer-a-sibling guidance despite payout-authorize/execute/status existing. The pointer to '/api/payout-contract' helps but is not usage routing.

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