WooCommerce: Delete product variation

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds real value by bounding the blast radius (parent product is preserved), but it does not explain the mechanism behind "or trash" — i.e. that force controls permanent deletion — nor what happens on a repeat delete despite idempotentHint=false.

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 front-loaded sentence with no padding; the destructive action and its scope come first. The "[UNIFIED]" prefix is the only low-value token.

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 destructive mutation with four undocumented parameters and no output schema, the description is too thin. It should state force semantics, the parent-vs-variation id relationship, and any confirmation/auth expectations for an irreversible operation.

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 0%, so the description must carry parameter meaning and largely does not. It implicitly frames product_id as the parent and variation_id as the child, and gestures at force via "or trash", but the required `site` parameter and the trash-vs-permanent behavior of force are left entirely undocumented.

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 (delete/trash), a precise resource (a single variation of a variable product), and a scope constraint ("without touching the parent product") that cleanly separates it from the sibling woocommerce_delete_product.

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?

Usage is only implied: the parenthetical "(or trash)" hints that some flag toggles the mode, but the description never says when to trash vs. permanently delete, nor does it name any alternative tool or precondition (e.g. needing the parent product_id).

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