shopify_cancel_order

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

The description discloses key behavioral traits: asynchronous (returns a job), destructive, requires confirm=true, and provides default values for reason, restock, refund, and notifyCustomer. Since no annotations are provided, the description carries full burden and does well.

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 a single, dense sentence that front-loads the main action and includes critical details without extraneous words. Every part adds value.

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?

Given the complexity (7 parameters, async, destructive), the description covers the main purpose, async nature, destructive flag, and defaults. It could benefit from mentioning the job return format or how to verify completion, but overall it is fairly 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 description adds meaning for some parameters (reason default, restock default, refund default, notifyClient omitted, confirm required) but does not describe id or staffNote. With 0% schema coverage, the description partially compensates but is incomplete for all 7 parameters.

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 tool cancels an order asynchronously. It uses a specific verb 'cancel' and resource 'order'. Among sibling tools, there is no other cancel tool, so it is well-distinguished.

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 implies usage for canceling orders but does not explicitly state when not to use it or suggest alternatives. It mentions the destructive nature and requirement for confirm=true, but lacks explicit guidance on context.

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