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

Annotations already declare a non-readonly, non-idempotent, destructive write, and the description adds real behavioral context beyond that: immediate publishing, remote image URL fetching (which explains the openWorldHint), duplicate creation on repeat calls, and the notable fact that local WordPress auth is used so no WooCommerce REST API keys are needed. It stops short of saying what is returned or what side effects publishing triggers (e.g., storefront visibility, notifications).

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?

Four short sentences, front-loaded with the core action and then the notable behaviors. Each sentence carries information; only the 'Mirrors woocommerce-mcp-server method' clause is slightly incidental, though it does justify the auth model.

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?

For a mutation tool with a free-form nested productData object and no output schema, the description should say what comes back (e.g., the new product ID needed for follow-up get/update calls) and whether publishing is reversible. Annotations cover the safety profile, but the return contract is left entirely unaddressed.

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 100% and site_id's schema text already explains the list_sites dependency, so the schema carries most of the weight. The description contributes one useful signal about productData contents — that image URLs can be supplied and will be downloaded — but gives no field-level detail for the permissive nested object.

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 specific verb and resource ('Creates a WooCommerce product') and ties it to the upstream method `create_product`, so the agent knows exactly what is being made. It does not explicitly distinguish itself from near-name siblings such as wc_create_product_variation or wc_create_product_category, relying on the names alone for that separation.

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?

Usage context is implied rather than stated: 'Can publish immediately' and 'Repeated calls can create additional products' tell the agent this is a non-idempotent write and warns against blind retries. However, there is no explicit when-to-use/when-not guidance and no named alternative for related operations like variations or attributes.

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