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

Beyond the annotations (readOnlyHint true, openWorldHint false, destructiveHint false, idempotentHint false), the description discloses that it performs no page fetch, no account access, no counterparty contact and no money movement, and that it returns a report with an Ed25519 signed receipt. It also reveals commercial behavior the annotations cannot: 0.10 USDC per call on Base via x402 exact, 10 free signed-wallet calls per rolling 30 days, and the requirement to bind X-Wever-Wallet-Proof to the exact JSON arguments and tool route.

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 purpose and the check list are front-loaded in the first two sentences, and each later sentence adds a distinct operational fact (endpoint, read-only scope, pricing, wallet proof, receipt, contract link). It runs long and mixes functional description with boilerplate links, but no sentence is pure repetition.

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 and a deeply nested six-parameter schema, the description does the needed work: it names everything the report validates and the ready/not_ready outcome with each missing or inconsistent element listed, plus the signed-receipt return. The only unresolved piece is the relationship to the payout-write siblings, which is left implicit.

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 already 100%, so the baseline would be 3. The description goes further by grouping the parameters by role (request fields, supporting invoice, documents, approvals, optional policy) and unpacking what the policy carries (required approvals, approver roles, required documents, maximum amount), which tells the agent how the inputs are consumed in the checks.

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 states a specific verb and resource: it submits a payout request (recipient, wallet, network, amount, currency, purpose, requester) with invoice, documents, approvals and an optional policy and returns ready or not_ready. It separates itself from the payout-authorize/create/execute/status siblings by declaring it reads only the material in the call with no money movement, though it never names those siblings 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 rather than stated: 'The report is the readiness record for whoever runs the payout' hints this is a pre-flight step before authorizing or executing a payout, and the contract link offers further guidance. But there is no explicit when-to-use/when-not statement and no named alternative such as wever_payout-authorize or wever_payout-policy-check, leaving the agent to infer the boundary.

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