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

Beyond the readOnlyHint:false annotation, the description explicitly warns 'WRITES: this call changes stored state and is not safe to repeat blindly.' It also discloses validation-before-write, that the submission is chained on the record, and the downstream consequences of a funder paying the bound address. This is strong behavioral disclosure with no contradiction.

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?

The description is dense but not bloated: it front-loads the purpose and then adds critical behavior, payout details, and side effects. It is a single wall of text with emphatic all-caps sections, but every sentence carries substantive information.

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 mutating tool with a nested payout object and no output schema, the description covers eligibility, artifact semantics, payout binding, validation order, and settlement effects. It does not describe response/error behavior or the unexplained `secret` parameter, leaving some gaps for an agent invoking it autonomously.

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 0%, and the description compensates well for artifact, note, listing_id, and the payout object including signature omission and signing_bytes semantics. However, the `secret` parameter is never explained, and some nested payout field semantics still rely on the caller's prior knowledge.

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 action ('Hand work in') against a concrete resource ('an open listing'), and clarifies what counts as an artifact and who may submit. It is clearly a submission tool and distinct from the surrounding listing/payout/award siblings, though it does not explicitly name an alternative tool to differentiate from.

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 gives clear usage conditions: any non-funder may submit to an open listing before expiry, with no claiming or reservation, and explains the optional payout payload to send along. It does not explicitly identify when to prefer a sibling tool, so some alternative-routing guidance is missing.

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