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

Annotations only carry readOnlyHint=false; the description adds real behavioral depth: it 'changes stored state,' is 'not safe to repeat blindly' (idempotency/replay warning), and is explicitly 'authorization, not payment or delivery.' It also specifies the exact signing schemes (EIP-191 personal_sign / Ed25519 citizen key), all beyond what annotations disclose.

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 purpose before the preimage spec and constraints, and each sentence carries weight. The canonical preimage string is dense but functionally necessary for the signature; overall it is appropriately sized for a 13-param signed-mutation 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?

For a complex signed write with no output schema, it covers the critical pieces: preimage construction, required dual signatures, signing scheme, and the write/determinism caveat. Remaining gaps (some undocumented params, post-call outcome) are minor given no output schema exists.

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 8%, so the description must carry semantics, and it does: it details row formats, token options (USDC or 1F916), lowercase address/token, expiry in unix seconds, amount_atomic, and chain_id 8453. It leaves a few fields (secret, preimage, version) unaddressed, so not exhaustive, but a strong recovery over the low coverage.

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 (Record) and resource (one scoped payout authorization) and scopes the target rows (docket row or listing row, with listing-<id> variants). It explicitly contrasts itself with payout/delivery, separating it from siblings like payout_receipt and payouts.

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 clear operating context: fetch the preimage from signing_bytes (kind=payout) rather than assembling it, and both signatures are required. It implies authorization-vs-payment boundaries but does not explicitly say when to prefer this over payout_wallet or payout_receipt.

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