WooCommerce: List product variations

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

Annotations already declare readOnlyHint=true, so the write-safety question is answered. The description usefully adds what the response contains (pricing, stock, attribute combinations per variation), but says nothing about pagination behavior, defaults, or ordering despite page/per_page parameters.

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?

Two tight sentences, front-loaded with the operation and followed by the return contents; nothing is padded. The '[UNIFIED]' prefix is unexplained tag noise that does not help an agent decide anything.

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?

With no output schema the return summary is genuinely needed and present, but the 0% parameter coverage and absent pagination semantics leave real gaps for a four-parameter tool. Adequate to call correctly for the common case, incomplete for edge cases.

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% for four parameters, and the description does not compensate: product_id is only obliquely implied by 'variable product', and page, per_page, and site are never mentioned. The agent must rely entirely on parameter names and JSON types.

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 gives a specific verb and resource ('List all variations of a variable product') and states the scope is limited to variable products, which differentiates it from list_products or get_product. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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?

There is an implicit prerequisite ('of a variable product'), but no explicit guidance on when to use this instead of woocommerce_get_product or woocommerce_list_products, and no statement of when it would return nothing. The agent must infer the usage context from the name alone.

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