woocommerce_create_product

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

With no annotations provided, the description carries full burden but fails to disclose idempotency, error handling (e.g., duplicate names), side effects, or that the default status is 'draft'. Only states the obvious 'create' operation.

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?

Compact and front-loaded, though the '[UNIFIED]' tag appears to be implementation metadata that doesn't help the agent. Otherwise efficient use of space without redundancy.

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 14-parameter creation tool with zero schema descriptions and no output schema, the description is insufficient. It lacks return value documentation, error scenarios, and detailed parameter guidance needed for correct invocation.

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 has 0% description coverage. While the description lists conceptual fields (pricing, inventory, categories), it doesn't explain critical parameter semantics like whether 'categories' expects IDs or names, the format for 'attributes', or valid values for 'type'.

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 WooCommerce products and specifies support for simple/variable types, distinguishing it from variation-specific siblings. However, it doesn't explicitly differentiate from woocommerce_update_product or clarify the '[UNIFIED]' prefix meaning.

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?

No explicit guidance on when to use this versus woocommerce_create_product_variation or prerequisites like authentication. The description assumes the agent knows when product creation is appropriate without contextual cues.

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