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

Annotations already declare readOnly/idempotent/non-destructive, and the description corroborates it explicitly: no fee, no gas, no money moves, none held. It goes further with things annotations cannot express — the packets' creator decides, acceptance holds packets, claims still pass the same admission, a person accepts every proof, rung progress is read from the Standing rather than the bidder, and all problems are surfaced before signing.

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?

It is a dense single block but front-loaded with the core action before the constraints and the sign-and-submit mechanics. The cost statement is duplicated ('no fee, no gas, NO money moves' then 'Cost and signer: free, no gas'), which is the main wasted sentence.

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 an 11-parameter nested tool with 7 required fields, it covers the full round trip: what to gather first, what is returned (MESSAGE_TO_SIGN and BODY_JSON), how to sign (personal_sign with the bidder wallet), the deadline, and who signs. With an output schema present, it does not need to describe return payloads in more detail.

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, but the description adds real semantics: shares must sum exactly to the price, the target rung must be exactly one above the current reading, and the payment rails are explained (usdc = the board's USDC rail on Base; token = your group's ERC-20 on Base 8453 or Robinhood Chain 4663), which enriches the rail/chainId enums.

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 first sentence states a very specific verb+resource+scope: offer one price for one condition of one place, one rung up, over open packets at that place. The title's '(step 1 of 2)' plus the explicit follow-up (submit_outcome_bid) makes its position in the flow unambiguous, and the rung ladder (Unread, Read, Tended, Kept, Whole) is enumerated.

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?

It names the prerequisite lookups (find_work near the place; place_standing for each condition's current rung) and the mandatory next step with a hard deadline (submit_outcome_bid within 5 minutes). It never contrasts with the many sibling prepare_* tools, notably prepare_bid, so the agent must infer when an outcome bid is preferred over a plain bid.

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