delete_store_product

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

Adds value beyond annotations by describing irreversibility, cascading deletion of variants, and the need for verification, which aligns with destructiveHint=true.

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?

Concise, with a clear structure: purpose, cautionary notes, Args, Returns. No redundant 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?

Provides sufficient information for a destructive tool, including irreversibility, scope, return value, and parameter details for required fields.

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?

Documents the two required parameters (store_id, product_id) with brief but clear descriptions, but omits the optional 'account' parameter, which is not explained in the schema either.

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 it 'Permanently delete a product and all of its variants from a store,' using a specific verb and resource, and distinguishing it from sibling tools like delete_store_product_variant.

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?

Includes explicit warnings: 'This cannot be undone,' 'Verify the product_id before calling,' implying cautious use, and contrasting with alternatives like delete_store_product_variant.

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