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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals the side effect of restoring listing stock and the hard limitation on canceling funded escrows. It could additionally mention what happens on invalid IDs or return behavior, but the core state-changing behavior is well disclosed.

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 sentences convey the action, precondition, side effect, and exclusion. There is no filler or repetition, and the critical state condition is front-loaded.

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 tool is simple with two parameters and no output schema. The description covers precondition, action, side effect, and fallback path, which is enough for correct invocation. A minor gap is the absence of any note about error/return behavior, but this does not materially hinder usage.

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 the parameters are already fully documented in the schema. The description does not add new parameter-level meaning beyond reinforcing that orderId refers to an order in Initiated escrow state, which is sufficient for the baseline.

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 action ('Cancels an order') and a precise resource with a qualifying state ('escrow is still Initiated'). It also clarifies the no-on-chain-funds condition, which differentiates this tool from other order-related siblings like confirm_delivery or get_order.

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?

Explicitly states when cancellation is valid (Initiated escrow), when it is not valid (Funded escrow), and directs the agent to the dispute/refund flow on the website instead. This gives clear when-to-use and when-not-to-use guidance.

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