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

Goes meaningfully beyond the annotations by disclosing the blast radius: other participants' holds persist, cleanup can resume, and canonical outcomes are unaffected. That is genuine effect-scoping context for a destructiveHint=true tool. It omits idempotency behavior (annotations say non-idempotent) and what a failed or repeated withdrawal does.

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, no filler, with the primary action front-loaded and effect constraints following. Every sentence carries distinct 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?

The effect scope is well covered for a destructive mutation with no output schema, but the ambiguity around the required 'id' and the absence of any failure/permission behavior leave real gaps for an agent trying to call it correctly the first time.

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 coverage is 0% and the description does not compensate. 'with a reason' loosely maps to the reason parameter, but the required 'id' is never explained — it is genuinely ambiguous whether it is the dispute id or the artifact id, and the tool name points the other way.

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 and resource ('Withdraw your own file-retention dispute') and scopes it to the caller's own disputes, which separates it from the sibling open_artifact_dispute. It stops short of naming the counterpart sibling explicitly, but the operation is unambiguous.

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: you call this to retract a dispute you filed. There is no explicit when-to-use vs. when-not, no mention of open_artifact_dispute as the inverse operation, and no stated prerequisite such as being the original filer or the dispute being open.

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