Delete Store

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

The destructiveHint annotation already signals that this is a destructive operation. The description adds no additional behavioral context, such as irreversibility, cascading deletes, or impact on related data (e.g., products, orders). Thus it provides no value beyond the annotation.

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, directly worded sentence with zero wasted words. It is appropriately front-loaded and concise for the tool's simple purpose.

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 of the tool (one parameter, no output schema) and the destructiveHint annotation, the description is minimally complete. However, it omits important contextual details for a destructive operation, such as whether deletion is permanent or cascades to associated resources. More guidance would improve completeness.

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 fully documents the single parameter store_id with a description 'Store ID'. The description adds no additional meaning about the parameter, so the baseline of 3 applies since schema coverage is 100%.

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 'Delete an ecommerce store.' uses a specific verb+resource combination, clearly distinguishing it from sibling tools like ecommerce_stores_create, ecommerce_stores_list, and ecommerce_stores_metadata. The purpose is unambiguous.

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?

No usage guidelines are provided. It does not state when to use this tool versus alternatives, nor does it mention any prerequisites, such as ensuring the store has no active products or orders before deletion. The agent gets no contextual guidance beyond the action itself.

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