woocommerce_create_product_category

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

No annotations provided, so description carries full burden. It mentions hierarchical support (behavioral capability) but fails to disclose mutation characteristics: idempotency behavior, what is returned upon creation, error conditions for duplicate names, or required permissions for WooCommerce category 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?

Two sentences that efficiently convey purpose and key feature. Slight deduction for '[UNIFIED]' prefix which appears to be metadata clutter that doesn't aid the AI agent's understanding.

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 4 parameters, 0% schema coverage, no output schema, and no annotations, the description is inadequate. It lacks explanation of the 'site' parameter, return value structure, and error handling despite the operational complexity of creating hierarchical taxonomies.

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 has 0% description coverage. Description mentions 'parent-child relationships' explaining the 'parent' parameter, but completely omits explanation of critical 'site' parameter (unclear if URL, ID, or slug) and 'description' parameter. With zero schema documentation, the description fails to compensate adequately.

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?

Description explicitly states 'Create a new WooCommerce product category' with specific verb and resource. It clearly distinguishes from siblings like 'wordpress_create_category' by specifying 'WooCommerce', and from 'woocommerce_list_product_categories' by specifying 'Create'.

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?

Mentions 'Supports hierarchical categories with parent-child relationships' which implies usage context for the parent parameter, but lacks explicit when-to-use guidance versus alternatives (e.g., when to use this vs wordpress_create_category) or prerequisites.

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