Create a WooCommerce product via WordPress REST API by setting a required name and optional price, stock, status, and description.
Add a WooCommerce product
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| status | No | ||
| sale_price | No | ||
| description | No | ||
| stock_status | No | ||
| regular_price | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It does not disclose permissions needed, side effects, whether the operation is destructive, or any other behavioral trait beyond the bare implication of 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 only four words and front-loaded, but it is under-specified rather than appropriately concise. It omits critical details needed to call a six-parameter mutation tool correctly.
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 a mutation tool with six parameters, no annotations, and no output schema, the description is wholly inadequate. It provides nothing about required inputs, behavior, or what the tool returns.
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% for all six parameters, and the description adds no parameter meaning at all. It does not explain the required 'name' field, acceptable values for 'status' or 'stock_status', or price formats.
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 states a clear verb ('Add') and resource ('WooCommerce product'), so the tool's basic purpose is immediately clear. It does not distinguish itself from siblings like wc_update_product or wc_products_search, which keeps it from a 5.
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 wc_update_product, no prerequisites, and no exclusions. The agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.