wordpress_wc_create_product

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

With no annotations, the description must disclose behavioral traits. While it implies a write operation ('Create'), it does not mention side effects, permissions required, or response behavior. The description is insufficient for understanding the tool's full impact.

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 extremely short (one clause), but it sacrifices necessary detail for brevity. Conciseness should not come at the cost of completeness; important context about parameters and usage is missing.

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 no output schema, no annotations, and minimal parameter info, the description fails to provide a complete picture. The agent lacks understanding of what the tool accepts, what it returns, and any prerequisites or side effects.

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 meaning beyond the schema field names. It does not explain what 'name' or 'regular_price' represent, any constraints, or how they relate to the product creation process.

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 verb 'Create' and the resource 'WooCommerce product', which distinguishes it from sibling tools like delete, update, get products. However, it could be more specific about the scope (e.g., 'with name and price').

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 guidance is provided on when to use this tool vs alternatives (e.g., wordpress_wc_update_product) or any prerequisites (e.g., WooCommerce must be active). The agent receives no context for decision-making.

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