delete_order

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

Annotations already indicate destructiveHint=true, but the description reinforces this with '🔴 DESTRUCTIVE · deletes data' and adds the important behavioral detail to confirm with the user. No contradiction with 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 repetitive: 'Delete an order', 'Deletes a record', 'Delete an existing e-commerce order resource.' could be consolidated. The tag line adds context but occupies space. Could be more concise without losing meaning.

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 simplicity (single param, no output schema), the description covers the essential action and safety warning. However, it lacks any indication of return value or confirmation behavior, which would be helpful for an agent.

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 input schema already describes the single parameter (ecomOrderId) with a clear description. Schema coverage is 100%, so baseline 3 is appropriate. The description adds no additional parameter semantics.

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 ('Delete an order', 'Delete an existing e-commerce order resource') and the resource type ('Ecom Orders'). It is specific and distinguishes from sibling tools like create_order, update_order, get_order.

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 explicitly instructs to 'Confirm with the user before calling', which is a critical usage guideline for a destructive tool. However, it does not elaborate on when to use versus alternatives like bulk operations or alternative deletion methods.

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