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

Goes well beyond the annotations: no fee, no gas, no credit moves or is held, no Regen address supplied (board derives the regen1 account from the signature), never prices the credit, one offer per wallet per packet with replacement semantics, a 5-minute signing window, and 'the house never holds a key'. These are exactly the behavioral facts an agent needs and are consistent with readOnlyHint=true.

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-loaded with the key framing ('Before the work') and dense with substance, but it is a single long block with real redundancy: cost/free/no-gas is stated twice, and signing is described twice ('personal_sign' vs 'signs the result with their own wallet or passkey'). Trimming the repeats would make it noticeably sharper.

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 two-step prepare tool this covers everything an agent needs: what is produced (MESSAGE_TO_SIGN and BODY_JSON), how to sign it, the 5-minute deadline, the submit_credit_offer handoff, the later settlement path, replacement semantics, and the exact state-based refusal rules. With an output schema present, return-value detail is correctly left out.

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 100%, so all six parameters are already documented. The description mostly restates the amount rule (own units, ≤6 decimals) that the schema already gives, adding only the interpretive gloss '1.5 means one and a half verified hours' and the note that no Regen address is needed. Useful but marginal over the schema — baseline 3.

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?

Specific verb + resource: prepare a signed offer to pay a work packet in VSH ecocredits from a named Regen batch on chain regen-1. The title and opening line make clear it is 'step 1 of 2' (prepare, not submit), distinguishing it from submit_credit_offer and from the sibling prepare_token_offer / prepare_direct_offer / prepare_backing paths.

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 timing ('Before the work'), the required follow-up ('sign with the backer wallet's personal_sign, then call submit_credit_offer within 5 minutes'), and the precise when-refused conditions (claimed, settled, expired, already funded) plus the creator/beneficiary exception. It does not explicitly route to alternative offer tools for other asset types, which keeps it 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.