wp_create_product

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, and it only states the creation action. It does not disclose default status (draft vs. published), uniqueness constraints on sku, whether duplicate names/skus are rejected, side effects on stock or inventory, or what the response contains. For a mutation tool with zero annotation coverage, this is a significant transparency gap.

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 single sentence contains zero wasted words and front-loads the core purpose, which is good. However, for a 12-parameter tool with no annotations and no output schema, a 7-word description is under-specified rather than appropriately sized — conciseness here crosses into insufficiency.

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 (12 parameters, 8% schema coverage, no annotations, no output schema), a one-sentence description is radically incomplete. The agent would need external knowledge to correctly construct a product payload, understand pricing/stock field interplay, and anticipate the tool's response. Nothing beyond the basic operation is conveyed.

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 only 8% — only 'name' is documented in the schema, leaving 11 of 12 parameters (sku, status, sale_price, manage_stock, stock_status, regular_price, stock_quantity, etc.) completely unexplained. The description adds nothing about parameters, so it fails to compensate for the near-total absence of schema descriptions. An agent has no way to know what values are valid for fields like stock_status or status.

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 'Create a new WooCommerce simple product' names a specific verb (create), a specific resource (WooCommerce simple product), and even qualifies the product type, which distinguishes it from generic siblings like wp_create_post and wp_create_cpt_item. It is clear enough for an agent to identify what this tool does, though it does not explicitly contrast itself with the many other create tools in the sibling list.

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 no guidance on when to use this tool versus alternatives such as wp_create_post, wp_update_product, or wp_create_cpt_item. No context about product-type constraints (simple vs. variable products), prerequisites like WooCommerce being active, or scenarios where a different sibling would be more appropriate. The agent must infer usage entirely from the name.

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