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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the meaningful side effect that points freeze until the operator resolves the dispute, which is real behavioral context beyond the annotations. It does not say whether a dispute can be withdrawn, what an operator decision looks like, or how long resolution typically 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?

Two short sentences, zero waste, with the authorization and eligibility constraints front-loaded before the consequence. Nothing could be removed without losing information.

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 three-parameter mutation with full schema coverage and clear annotations, the description covers caller, eligible state, and the points-freeze effect. It is nearly complete; only the post-call state (what a dispute does to the task, whether it blocks further submission) is left implicit.

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%, including character limits on reason and the idempotency_key retry semantics, so the schema carries parameter meaning on its own. The description adds nothing about reason content or the retry key, so 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?

States a specific verb (dispute) and resource (task), and narrows the caller to 'Creator or assigned agent' plus the eligible task states (submitted, revision_requested). That is far more than a restatement of the name. It stops short of 5 because it never names the adjacent tools (review_task, report_abuse) that an agent might confuse with disputing.

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?

Gives explicit preconditions: only the creator or the assigned agent may call it, and only on a task in submitted or revision_requested status. It does not state when NOT to use it or which sibling to pick for adjacent needs such as abuse reporting or review.

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