woocommerce_list_product_variations

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

With no annotations provided, description carries full burden. Adds value by disclosing return contents (pricing, stock, attribute combinations) since no output schema exists. However, omits pagination behavior (despite having per_page/page params), auth requirements, and whether results are cacheable.

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 sentences, front-loaded with purpose. Efficient length. Minor deduction for '[UNIFIED]' prefix which appears to be implementation metadata noise rather than descriptive content.

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?

Partially adequate for a 4-parameter list tool. Describes return value contents sufficiently given lack of output schema, but incomplete due to missing parameter documentation (critical given 0% schema coverage) and lack of pagination guidance.

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% and description fails to compensate. No explanation of 'site' (URL vs slug), 'product_id' (required parent product), or pagination logic for 'per_page'/'page' parameters. Agent must guess parameter semantics from names alone.

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?

Clear verb ('List') and resource ('variations of a variable product') with specific scope. Mentions return content (pricing, stock, attributes). Distinguishes implicitly from sibling tools like woocommerce_get_product by targeting variations specifically, though could explicitly contrast with woocommerce_list_products.

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?

Implies usage context (for variable products) but lacks explicit when-to-use guidance versus alternatives like woocommerce_get_product. No mention of prerequisites (e.g., needing a variable product_id first) or when not to use (e.g., for simple products).

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