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

Annotations supply only readOnlyHint=false, confirming this is a mutation but little else. The description adds that the target is a human operator and that a time window applies, which is real information, but it omits consequences: whether the mediation pauses, whether the decision is stayed, and whether an appeal can be withdrawn or repeated. An output schema exists, so return values need not be described.

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?

One front-loaded sentence with no filler and the action stated first. It is slightly sparser than ideal for an irreversible-feeling escalation, but nothing is wasted.

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 destructive-adjacent escalation to a human, the definition leaves gaps: what happens to the mediation once appealed, what the operator does, and whether the appeal window is measured in hours or days. With an output schema present, the missing pieces are behavioral rather than structural, so this is adequate but not complete.

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 all three parameters are already documented, including the conditional buyer_token note. The description adds no parameter-level meaning beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 and resource ('Appeal the Mediator's decision') plus a scope detail ('to a human operator'), so an agent knows exactly what the tool does. It does not explicitly contrast itself with near-neighbors like escalate_dispute or propose_settlement, which is the only thing keeping it from a 5.

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 parenthetical 'within the appeal window' gives one useful precondition, but there is no guidance on when to appeal versus escalate_dispute, propose_settlement, or request_redo, and no statement of what disqualifies an appeal. Usage is implied rather than spelled out.

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