Create WooCommerce Product

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

Annotations already mark this as a mutating, non-idempotent operation. The description adds one useful behavioral fact (Tickera bridge mapping availability) and a claim that it 'supports simple products with price, description, categories, and images.' However, the latter is vague and could imply that only simple products are supported, which contradicts the schema's enum of product types. There is no mention of auth requirements, error behavior, or result contents.

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 and immediately front-loads the core purpose. The first sentence is direct, the second provides a specific use-case. The final sentence about 'simple products' is somewhat redundant with the schema but not wordy. Overall it is compact and scannable, though the last sentence could be trimmed.

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?

With 14 parameters and no output schema, the description should explain return behavior or at least confirm what happens on success—it does neither. It does provide key context about Tickera mapping and product capabilities, but the missing result information and ambiguity about non-simple product types leave the tool only partially contextualized. The schema fills many gaps, but the description alone is not fully complete.

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 coverage is 100% (all 14 parameters have descriptions), so the baseline is 3. The description adds extra meaning to the 'type' parameter with the Tickera guidance and groups key parameters (price, description, categories, images), which helps the agent understand typical usage. This lifts it above the baseline.

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 opens with a clear, specific verb and resource: 'Create a new WooCommerce product.' This directly distinguishes it from siblings like wc_update_product and wc_list_products by the action 'create'. It also adds a domain-specific note about Tickera ticket products, which further clarifies its role.

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 gives a concrete usage guideline: 'For Tickera ticket products, set type='simple' and the product will be available for Tickera bridge mapping.' This tells the agent when and how to use the tool for a specific scenario. It doesn't explicitly exclude alternatives (e.g., 'use wc_update_product for existing products'), but the word 'create' implies the distinction well enough.

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