Delete Shopify Product

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

Annotations already declare destructiveHint and non-readonly, but the description goes well beyond by disclosing the irreversible cascade of destroyed entities, the 'cannot be undone' warning, and the compensating effect on orders. This is exactly the extra context a destructive tool needs.

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?

Four tightly-scoped sentences, front-loaded with the destruction scope and irreversibility, then the safer alternative, then the order caveat. No filler.

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?

No output schema is present or needed for a delete. The description covers scope, irreversibility, the recommended alternative, and the order side-effect — everything an agent needs to call this safely.

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?

Schema description coverage is 100%, so productId (GID) and confirm are already documented in the schema. The description adds no parameter-specific syntax or format detail, so baseline 3 applies.

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?

States a specific verb ('PERMANENTLY delete') and resource ('a product'), then enumerates the cascade (variants, media, inventory items, collection memberships). This clearly distinguishes it from sibling mutations like shopify_update_product and shopify_delete_variants.

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?

Explicitly routes the agent: 'Prefer setting status to ARCHIVED via shopify_update_product if there is any chance you'll want it back.' Names the alternative tool and the condition that selects it, and clarifies a non-obvious boundary (completed orders unaffected).

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