woocommerce_create_product_variation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It successfully explains the domain concept (what a variation is), but omits critical operational details such as error behavior when product_id doesn't exist, authentication requirements, or whether the operation is idempotent. The 'Create' verb implies mutation, but safety characteristics are unspecified.

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 consists of two efficient sentences with no redundancy. The '[UNIFIED]' prefix appears to be metadata noise that adds no semantic value for tool selection, but the remaining content is well-structured and front-loaded with the core action.

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?

Given high complexity (11 parameters, 0% schema coverage, no output schema, no annotations), the description is insufficient. It explains the WooCommerce domain concept adequately but fails to provide the necessary API mechanics—specifically parameter formats, validation rules, and return behavior—that would enable an agent to invoke the tool correctly without external documentation.

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 description coverage across 11 parameters, the description inadequately compensates. While it conceptually maps 'attributes,' 'pricing,' and 'inventory' to their respective parameter groups, it fails to explain critical required parameters like 'site' (string format/expected values) and 'product_id' (must reference an existing variable product). The 'attributes' array format remains unexplained despite being complex and required.

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 creates a 'variation for a variable product' and explains that it defines a 'combination of attributes with its own pricing and inventory.' This distinguishes it from siblings like woocommerce_create_product (which creates the parent product) and woocommerce_create_product_attribute (which creates attribute definitions). It lacks explicit prerequisite mention (that a variable product must exist first), preventing a perfect score.

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 implies usage context by specifying 'variable product,' suggesting this should not be used for simple products. However, it fails to provide explicit when-to-use guidance (e.g., 'use after creating a variable product') or mention alternatives like woocommerce_list_product_variations for retrieval or woocommerce_update_product for modifying the parent product.

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