delete_store_product

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

The description goes beyond annotations by detailing the irreversible nature ('cannot be undone'), concurrency limit ('Max 10 concurrent requests'), and support for read-only/dry-run modes. This adds substantial behavioral context beyond the annotations (readOnlyHint=false, idempotentHint=true, 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?

The description is concise, with every sentence adding value. It is front-loaded with the primary action, followed by warnings, authentication, and parameters. No redundant or missing 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 output schema exists (not shown but indicated), the description appropriately covers return values ('JSON confirming deletion'). It also addresses the destructive nature, authentication, and rate limits, making the tool fully self-contained 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?

With schema description coverage at 0%, the description fully explains all three parameters: store_id, product_id, and the optional account name. It adds meaning about the account parameter including environment variable configuration and fallback to default.

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 tool to 'Permanently delete a product and all of its variants from a store.' It specifies the verb (delete), resource (product and its variants), and scope (from a store). This distinguishes it from siblings like delete_store_product_variant or delete_store.

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 includes important usage guidance such as 'Verify the product_id before calling' and authentication details. However, it does not explicitly contrast with sibling tools like delete_store_product_variant, leaving the agent to infer when to use this tool vs alternatives.

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