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

Annotations already declare readOnly=false and destructive=false, so the safety profile is largely covered by structured data. The description adds real behavioral context beyond that: funds stay held rather than being released, and Rooms staff adjudicate the outcome with a credit/refund path. It does not contradict any annotation, though it omits whether a dispute can be cancelled or how long resolution takes.

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 sentences that front-load the use condition, then state the action and the consequence. No filler, no restatement of the title or schema.

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 two-parameter mutation with annotations and no output schema, the definition covers trigger, scope, and the key downstream consequence (payment held, staff resolution, possible credit). The main remaining gap is outcome timing and whether the dispute is reversible.

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%, with both job_id and reason documented in-schema, so the baseline is 3. The description mentions only "the work submitted for a job" generically and adds no format or constraint guidance for reason beyond the schema's maxLength.

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?

"Dispute the work submitted for a job your user opened" gives a specific verb and resource plus a scope constraint (only jobs your user opened). It is clear enough to distinguish from accept_job, but it never names the closest alternatives such as request_revision, so the agent must infer differentiation from names alone.

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 opening sentence supplies an explicit trigger condition ("Use when submitted work is unacceptable"). There are no stated exclusions or named alternatives, so the agent is not told when request_revision or accept_job would be the better call, which keeps this below a 5.

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