delete_store_product_variant

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

Exceeds annotations by stating permanence, undo impossibility, rate limits, read-only/dry-mode respect, and constraint on last variant. Annotations only indicate destructiveHint and idempotentHint; description adds critical behavioral context.

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 a clear structure: action, consequences, constraints, auth, args, returns. Each sentence adds value, no redundancy, and front-loaded with the main purpose.

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 simple delete operation with 4 parameters, shema coverage 0%, output schema present (implied), the description covers purpose, constraints, auth, rate limits, parameter semantics, and return value. No gaps for effective use.

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 0% schema coverage, the description provides detailed parameter explanations including store_id, product_id, variant_id, and account with naming convention and default behavior, fully compensating for missing schema descriptions.

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 deletes a single variant from a product permanently, with the verb 'delete' and resource 'store product variant'. It distinguishes from siblings like delete_store_product and delete_store_product_image through specificity.

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?

Provides usage guidelines like max concurrent requests, auth via API key, and that deleting the last variant may be rejected. Implicitly differentiates from other delete tools by naming, but lacks explicit when-to-use or when-not-to-use comparisons.

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