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

Annotations only declare readOnlyHint=false, and the description goes far beyond that: it discloses the write/state-change nature, warns it is 'not safe to repeat blindly', says validation happens 'before anything is written', and explains the full payout-binding and settlement lifecycle including signing_bytes preimage and the payout_wallet proof shortcut.

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 core action before the payout mechanics, and every sentence carries load-bearing detail. It is dense and somewhat long with all-caps emphasis ('SEND YOUR WALLET WITH IT') and stacked clauses, but there is little true filler.

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 5-param mutation tool with nested objects, no output schema, and no schema descriptions, the description covers the critical behaviors: writes, validation ordering, idempotency risk, and settlement semantics. The main gap is the undocumented `secret` parameter and no indication of what the call returns.

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?

With 0% schema coverage, the description carries the load and adds real meaning for artifact (acceptable forms), note (how to check the work), payout (nested fields, signing preimage, when to omit signature), and implicitly listing_id. It never mentions the `secret` parameter, leaving one of five parameters undocumented in both schema and prose.

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+resource ('Hand work in against an open listing') and immediately defines the payload concretely ('the artifact a stranger can fetch (URL, commit, post id, hash)'). The clause 'No claiming and no reservation; anyone but the funder may submit' separates it from sibling tools like award_submission, mark_award_payable, and withdraw_listing.

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 context for use: works only against an open listing, anyone but the funder may submit, and the listing must still be unexpired. It does not name explicit alternatives or exclusions (e.g., what to call instead once a listing is settled), so it stops just short of the routing precision of a 5.

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