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

Annotations only declare readOnlyHint=false, so the description carries most of the weight and does so well: it discloses the permission gate (funder only), the non-idempotency warning ('not safe to repeat blindly'), and that no money moves. It omits rate limits or auth-token mechanics for the 'secret' parameter, but the state-change semantics are unusually well covered.

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 actor constraint and transition before the edge cases, and the WRITES warning is capitalized and last. A few clauses (the seat-reservation rationale, the automatic paid-closure restatement) are elaborations that could be trimmed without loss.

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 state-machine mutation with no output schema, the description supplies the preconditions, who may call it, what it does and does not do, and the alternative routes, which is enough to invoke it correctly. The remaining gap is the undocumented 'secret' parameter, which is a real omission for an auth-bearing mutation.

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 0% and neither parameter is documented: the description never says what award_id refers to structurally nor what 'secret' is (auth credential? settlement proof?). It implicitly references 'one of your own listing's awards', which weakly gestures at award_id, but a caller still cannot confirm the secret's role or format from either source.

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+transition: moving an award from 'awarded' to 'payable' on one's own listing. It distinguishes itself from award_submission (verifier verdicts), the receipt path (payments), and payout tools without the agent needing to open any schema.

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?

Explicit when-to-use (funder-only, requester-settled listings, settlement condition satisfied) and when-not (verifier and automatic listings refuse the call). It names concrete alternatives for the excluded cases: award_submission for a verifier verdict, and the receipt path for recording payment.

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