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

Beyond the destructiveHint=true annotation, the description discloses that cancellation refunds the charge to the wallet, explains the label-timing cutoff and rejection behavior, and advises confirming with the user. These details materially help an agent understand the consequences and prerequisites of the mutation.

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?

The description is three tight sentences with no wasted words. The core action, timing restriction, and destructive warning are front-loaded in an order that supports safe agent behavior.

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 mutation tool with annotations and an output schema, the description covers the necessary behavioral context: what it does, refund consequence, timing prerequisite, rejection outcome, and user confirmation. Nothing critical is missing.

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 100%, so the order_id parameter is already fully documented in the schema. The description reinforces the finalized-order context but adds no new syntax, format, or constraint details beyond what the schema provides.

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 (Cancels) and resource (a finalized order), making the tool's core action immediately clear. It does not explicitly differentiate itself from sibling cancellation tools such as cancel_my_event_registration or cancel_program_registration, which keeps it from a perfect score.

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 description gives a clear operational condition: it only works before order labels have been sent, otherwise the request is rejected. It does not mention alternative tools for managing lunch orders, but the timing constraint is sufficient guidance for correct use.

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