Execute Order Cancellation

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

Annotations already declare destructiveHint=true, and the description reinforces this with 'actually cancels the order.' It adds the production store requirement for confirm_production, which is not in annotations. No contradiction. The description provides useful behavioral context beyond the structured fields.

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, front-loaded with the primary purpose and a key caveat. Every sentence adds value: the first states the action, the second emphasizes the destructive nature and the production requirement. No fluff.

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 description covers the core action, the prerequisite (previewed), and an important setting. Given the annotations plus full schema coverage and the straightforward plan-preview-execute pattern, this is sufficient. It doesn't detail response behavior, but no output schema exists and the context is simple enough that this is not a major gap.

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% and all parameters have adequate descriptions, including operation_id referencing 'order_cancel_plan' and confirm_production's purpose. The description does not add further parameter details, but the schema carries the load, so a baseline of 3 is appropriate.

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 clearly states the action: 'Execute a previewed order cancellation.' The verb 'Execute' and resource 'order cancellation' are specific, and 'This actually cancels the order' distinguishes it from preview/plan steps, aligning with the sibling tool names.

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 indicates this tool is for executing a previously previewed cancellation, implying it follows order_cancel_plan and order_cancel_preview. It adds the critical condition 'Production stores require confirm_production: true,' but does not explicitly name alternatives or exclusions. The context is clear enough for typical usage.

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