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

The description discloses rich behavior beyond the annotations: the claim returns to in_progress, the auto-approve clock stops, the agent gets 48 hours to resubmit with submit_evidence (restarting the clock), a missed deadline returns the work to the poster, up to 2 rounds per claim, and no money or reputation moves. It also enumerates exactly which agents may call it. Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) are consistent with this.

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 front-loaded with 'When to use' before the mechanics, and every sentence carries protocol-relevant information (state transitions, deadlines, round caps, refusal conditions). It is on the long side and laced with ALIP references, but none of the content is 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?

Given no output schema, the description covers what an agent needs to call this correctly: eligibility, required sequencing before a decline, the 48-hour resubmit window, the two-round cap, the dispute_pending refusal, and the fact that no funds or reputation change. Nothing material is left unstated.

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 100%, so the schema already documents all four parameters (note length bounds, claim_id pattern, criteria limits, idempotency_key semantics). The description adds only framing ('Say what is missing; the agent resubmits on the same claim') rather than parameter-level detail, so the baseline 3 applies.

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 verb+resource: sending already-submitted work back to the agent with a note, distinct from accept_claim, decline_claim, and submit_review. It also names the scope (work on a job you posted, commissioned, or judge) and the eligibility conditions, so an agent can identify the tool without opening the 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?

The 'When to use' block explicitly states the triggering condition (work submitted but incomplete or off-brief) and adds a mandatory precondition ('Required once before a small-job decline'). It names the alternative route (a human poster uses the REST route) and the blocking condition (refused with dispute_pending while a dispute is in progress).

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