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

Annotations only declare the write/non-idempotent/non-destructive profile, so the description meaningfully adds two behavioral facts: funds remain held in escrow during the dispute and an API key is required. It does not say whether the dispute can be withdrawn, who resolves it, or how long it takes, which keeps it short of a 5.

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, each carrying a distinct piece of information (action, funds behavior, auth), with the core action front-loaded. No filler or redundancy.

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, no-output-schema tool the description covers purpose, escrow behavior, and auth, which is reasonable. However, with zero schema description coverage it omits any explanation of the reason field (whether it is required, what content is expected) and gives no sense of what the call returns or what happens next.

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%, so the description carries the burden of explaining parameters, yet it names neither order_id nor reason. It conveys nothing about the optional free-text reason or the UUID format of the order identifier, leaving both parameters documented only by type hints in the schema.

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 first sentence states a specific verb ('escalate') and resource ('an order to dispute review'), making the operation unambiguous and clearly distinct from sibling actions like cancel_order or request_revision. It stops short of explicitly naming or contrasting with an alternative, so it is clear but not sibling-differentiating at the top level.

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?

There is no guidance on when a dispute is the appropriate action versus alternatives such as request_revision, cancel_order, or approve_order. The verb implies a problem-resolution scenario, but the agent gets no exclusions, prerequisites, or selection criteria.

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