delete_store

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

The description discloses critical behavioral traits beyond annotations: the destructive cascade (removing products, variants, customers, carts, orders) and irreversibility. This adds significant value as annotations only provide destructiveHint and idempotentHint, which are consistent and not contradicted.

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 concise (3 sentences plus Args/Returns), front-loaded with the essential action and warnings, and structured with clear sections. No superfluous information.

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 tool's complexity and existing output schema, the description covers the key points: deletion scope, irreversibility, return format. Could mention that the store must exist beforehand, but overall sufficient.

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 explains the required parameter (store_id) meaningfully. However, with 0% schema coverage, the optional parameter (account) is not described at all. The description partially compensates for low schema coverage but is incomplete.

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 ('permanently delete an e-commerce store'), identifies the specific resource (store), and distinguishes it from sibling delete tools (e.g., delete_store_cart) by emphasizing the cascade effect.

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 provides clear context by warning that the operation is destructive and cannot be undone, advising careful verification of store_id. However, it does not explicitly state when to use this tool versus alternatives (e.g., deleting sub-entities separately), missing explicit usage guidance.

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