WooCommerce: Delete product category

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description adds real value beyond that by disclosing the cascade behavior (contained products are not deleted, WooCommerce re-assigns them) and the no-trash constraint. It stops short of stating required permissions or the response shape, which keeps it below a 5.

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?

Three short, front-loaded sentences with no filler; the destructive verb leads and the side-effect caveats follow. Nothing is wasted, though the sentences are not organized into an explicit 'when to use / what happens' structure.

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 low-complexity, two-parameter delete with annotations covering the destructive profile and no output schema, the description supplies the essential missing context: permanence, product reassignment, and the no-trash rule. The only notable gap is parameter documentation, which is minor at this complexity.

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%, so both parameters (site, category_id) carry no documented meaning in the schema. The description does not compensate — it never explains what site refers to or that category_id must be an existing category identifier — though the parameter names are largely self-explanatory for this simple two-parameter tool.

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?

States a specific verb and resource — "Permanently delete a WooCommerce product category" — which unambiguously separates it from sibling deletes such as woocommerce_delete_product, woocommerce_delete_product_attribute, and wordpress_delete_category. The word "Permanently" plus the resource name leaves no ambiguity about scope.

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?

Conveys implied usage (destructive removal of a category) and adds the constraint that categories cannot be trashed, which hints this is the only removal path. However, it never names an alternative or states when an agent should instead use a different delete tool or an update-based workaround.

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