create_product

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

Annotations are minimal (only openWorldHint: false), so the description carries the burden. It discloses one key behavioral trait: that for variable products, the tool only creates the parent and variants must be added via create_variation. However, it does not mention other behavioral aspects such as permission requirements, response format, or side effects beyond creation.

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 is two sentences, front-loaded with the primary purpose. The second sentence adds essential guidance for variable products without any fluff or repetition of schema information.

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 the complexity of 21 parameters, the description provides sufficient context for the most complex scenario (variable products) and the schema covers all parameter details. No output schema exists, but the description's focus on the variable product workflow makes it quite complete for a create 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 100%, so parameters are already well-documented. The description adds extra meaning by instructing to set type='variable' and include the attributes array for variable products, which reinforces the semantics of those parameters beyond the schema.

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 'Create a new WooCommerce product' with a specific verb and resource. It also distinguishes the tool's scope by noting that for variable products, the type must be set and attributes included, then create_variation is used for variants, which differentiates it from sibling tools like update_product and 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?

The description explicitly explains when to use this tool for variable products ('set type='variable' and include attributes array') and directs the user to an alternative tool for the next step ('then use create_variation to add variants'). This provides clear when-to-use and alternative guidance.

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