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

Goes well beyond the readOnlyHint/destructiveHint=false annotations: no fee, no gas, no money moves and none is held, the board reads balanceOf/symbol/decimals but never prices the token, re-offering replaces the prior offer, and the house never holds a key. These are exactly the behavioral facts an agent needs and none of them are recoverable from the annotations.

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 timing ('Before the work') and the zero-cost guarantee, then flows into mechanics and the follow-up call. Slightly redundant: 'FREE — a signed offer, no fee, no gas, NO money moves' is restated at the end as 'Cost and signer: free, no gas'.

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?

Covers timing, cost, signer, on-chain reads, refusal conditions, the follow-up submit step and its 5-minute window, and names the return payload. With an output schema present, nothing an agent needs to invoke this correctly is missing.

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 100%, so the baseline is 3; the description still adds meaning by tying backerWallet to the signing/paying identity, clarifying that amount is atomic and that the token's decimals are read on chain, and explaining that the token has no board-assigned price. Minor duplication of schema facts (atomic units, chain IDs) keeps it from a 5.

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 ('offer to pay this packet in a token'), scopes it to an arbitrary ERC-20 on Base or Robinhood Chain, and frames it as step 1 of 2 with submit_token_offer as step 2. It never explicitly distinguishes itself from the other offer tools (prepare_direct_offer, prepare_credit_offer, prepare_funding), which is the main gap for a family this crowded.

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?

'Before the work' plus the full sequence (sign with personal_sign, then call submit_token_offer within 5 minutes) tells the agent exactly when and how to invoke it. It also lists refusal states (claimed, settled, expired, already funded) and the one-offer-per-wallet-per-packet rule. Missing only an explicit statement of when a sibling offer tool would be the better choice.

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