delete_order

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

The description reveals a behavioral nuance beyond the destructiveHint annotation: the default operation is a soft delete (trash) and force=true changes it to permanent deletion. This additional context is valuable and not present in the annotations.

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 two-sentence, front-loaded statement with no extraneous content. It efficiently communicates the core action and the key behavioral option.

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 schema and annotations, the description covers the essential behavior and the main parameter nuance. It does not explicitly describe the return value, but the presence of a 'fields' parameter in the schema implies a response object, making the description 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 all parameters with 100% description coverage. The description further clarifies the force parameter by stating it overrides the default trash behavior, adding semantic value beyond the schema's 'True to permanently delete'.

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 'Delete an order' with a clear verb and resource. It also introduces the trash behavior, which distinguishes it from a hard delete and sets expectations for the delete operation.

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 does not explicitly name alternatives, but it offers clear usage context: 'Moves to trash by default; set force=true to permanently delete.' This guides the agent on when to use the tool and how to adjust behavior, even without explicit exclusions.

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