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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful outcome context — the poster accepts or rejects and pays the wallet directly. It does not, however, clarify resubmission behavior despite idempotentHint=true, nor what happens to the claim if proof is rejected.

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?

Two tight sentences with the action front-loaded and the proof formats parenthetically inlined; nothing is wasted. Brevity works against it only insofar as the space saved was needed for parameter context.

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?

This is a mutating, credential-bearing tool with four required undocumented parameters and no output schema. The description omits token/auth expectations, error behavior, and resubmission semantics — too much is left unspecified for an agent to call it confidently.

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% across four required parameters, so the description must carry the burden and largely fails. It explains 'proof' well (link, tx hash, or short report) but says nothing about job_id, claim_id, or the sensitive claim_token, leaving an agent to guess credentials and identifiers.

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 names a specific verb and resource ('Hand in proof ... for a claim') and even enumerates acceptable proof formats (link, tx hash, short report), so the action is unmistakable. It stops short of differentiating from the sibling 'deliver_work', which an agent could easily confuse with this tool.

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?

Usage is only implied: the phrase 'for a claim' suggests this happens after claiming a job, and the second sentence sketches the downstream accept/reject flow. There is no explicit when-not guidance, no prerequisites (e.g. where claim_token comes from), and no statement about how this differs from deliver_work.

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