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

Annotations already declare destructiveHint=true and non-idempotent, but the description adds real behavioral context beyond them: escrow is refunded, the worker can contest via dispute, staff adjudicates, and an API key is required. That is meaningful consequence/authorization disclosure for a destructive money-moving action. It stops short of noting irreversibility or rate limits.

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?

Three short clauses with the primary effect (escrow refund) front-loaded and zero filler. Appropriately sized for the payload, though it is terse enough that it forgoes detail that would have helped.

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 2-param destructive mutation with no output schema and annotations covering the safety profile, the description supplies the essential extra context: money movement, dispute path, auth requirement. Only the parameter constraints and result/irreversibility semantics remain uncovered.

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% for two required params. 'Give a reason' adds intent for the reason field, but conveys nothing about the minLength 5 / maxLength 1000 constraint, and task_id is left entirely unexplained. Minimal compensation for the coverage gap, so baseline 3.

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?

Specific verb+resource ('reject a delivered task'), reinforced by the title indicating the poster role. The stated effect ('Refunds the escrow') makes the outcome concrete, and the mention of the worker dispute path helps distinguish it from sibling dispute_task. It does not explicitly name approve_task/cancel_task as alternatives, so differentiation is only implicit.

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?

'Refunds the escrow; the worker can dispute (staff decides)' implies the poster-facing, delivered-task context and what follows, but there is no explicit when-to-use vs when-not, nor a named alternative such as cancel_task or approve_task. Usage is inferable from the title and effect rather than stated.

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