wafle_orders_cancel

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

Despite annotations already indicating destructive and idempotent behavior, the description goes beyond them by specifying that the order moves to 'cancelled', inventory is restocked, and the refund condition (gateway support and payment status). It also includes the crucial instruction to confirm with the user, providing rich behavioral context.

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 concise, with two sentences that each add essential information: the core action and the destructive consequences plus user confirmation. There is no waste or redundancy, and the structure is easy to parse.

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 operation without an output schema, the description covers the key behavioral aspects, including cancellation, refund, inventory restock, and user confirmation. It does not explain return values or error cases, but given the side effects are clearly disclosed, it is reasonably 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?

The schema covers only 2 of 4 parameters with descriptions, and the tool description does little to clarify the missing ones (reason, order_id). It indirectly explains the 'refund' parameter via the auto-refund note, but fails to add meaning for the other parameters, leaving gaps that the schema does not fill.

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 begins with 'Cancel an order,' a specific verb and resource, clearly distinguishing it from other order-related tools like wafle_orders_refund or wafle_checkout_order_refund. The extra detail about auto-refund further clarifies its unique role.

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 clearly implies the tool is for canceling orders, but it does not explicitly state when not to use it or mention alternatives. However, the context is unambiguous and the guidance to confirm with the user adds practical usage direction.

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