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

Far exceeds the annotations: it discloses idempotency mechanics (persisted transfer nonce prevents duplicate payment on retries), the return payload (executed status, confirmed tx hash, signed receipt), the auth header requirement (X-Wever-Wallet-Proof bound to exact args and path), and the paid-call pricing model. It also clarifies no private keys are accepted and funding/sweep remain manual, which materially shapes agent behavior.

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 action, preconditions and return value are front-loaded, which is good, but the description is bloated with pricing detail and legal/marketing filler ('A disbursement primitive, not a bank: no yield, conversion or fiat', 'Company-authored; usage remains explicitly labeled') that dilutes the actionable content.

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?

Given no output schema, the description still explains the return shape (executed status, independently confirmed tx hash, signed receipt). Authentication, idempotency, fees and the manual-custody model are all covered, so an agent has everything needed to invoke it 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 0%, so the description must compensate. It conveys the semantics of idempotency_key (nonce preventing duplicate payment on retries) and the fact that payout_id must reference an authorized mandate, though it doesn't restate the format constraints (po_ prefix, key charset) that 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?

States a specific verb and resource ('Disburse native USDC on Base from the dedicated service-operated payout wallet') with the exact precondition (authorized payout with a valid unexpired holder-bound mandate). This clearly distinguishes it from siblings like wever_payout-authorize, wever_payout-create and wever_payout-status.

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?

States the gating condition for use ('only for an authorized payout with a valid unexpired holder-bound mandate') and points to /api/payout-contract for the authorization flow, which implies the prerequisite authorize step. It never names an alternative sibling explicitly (e.g. when to use authorize vs execute), so it stops short of a 5.

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