Delete a product variant

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

Annotations already cover destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is established. The description adds 'single' to clarify scope but no further behavioral context such as permanence or side effects, which is acceptable given the annotations.

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?

A single, short sentence with no unnecessary words. It is front-loaded with the action and object, making it immediately understandable.

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?

For a straightforward delete operation with three well-documented required IDs and annotations covering idempotency and destructiveness, the description is sufficient. It lacks alternative routing and response information, but these are minor constraints for a simple delete tool without an output schema.

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 schema provides 100% coverage with descriptions for store_id, product_id, and variant_id. The description adds no parameter-level meaning beyond what the schema already supplies, matching the baseline for high schema coverage.

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 states the verb 'Delete' and the resource 'single variant from the product', making it specific and unambiguous. The word 'single' distinguishes it from batch variant operations, and 'variant' differentiates it from product-level deletion.

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 gives no guidance on when to use this tool versus alternatives such as ecommerce_updateProductVariantsInBatchV1 or ecommerce_deleteAProductV1. There is no mention of exclusions, prerequisites, or when a different tool would be more appropriate.

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