wordpress_wc_create_product

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

No annotations are provided, so the description carries the full burden. It only states the basic action ('create') without disclosing side effects, permissions, default values, response format, or any constraints. The minimal wording does not inform the user about what happens 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 a single, concise sentence with no superfluous words. It is front-loaded with the action and resource, making it easy to parse quickly.

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 minimal schema (2 params, no descriptions) and no annotations or output schema, the description offers very little context. It does not mention what additional product fields can be set, whether a product ID is returned, or any preconditions/limitations. The tool is under-specified for practical use.

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%, and the description adds no parameter semantics. While 'name' and 'regular_price' are somewhat self-explanatory, there is no explanation of expected formats (e.g., regular_price as string), required values, or how these fields map to WooCommerce data. The description fails to compensate for the lack of schema descriptions.

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 product' uses a specific verb ('create') and clearly identifies the resource ('WooCommerce product'). It distinguishes from sibling tools like update, get, and delete by explicitly naming the action and entity.

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 provides no guidance on when to use this tool versus alternatives, such as prerequisites (e.g., WooCommerce must be active) or context for when to choose product creation over other product-related operations. No exclusions or alternative references are mentioned.

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