wc_delete_product_brand

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

No annotations are provided, so the description carries the full behavioral burden, and it largely fails to do so. It does not disclose the critical WooCommerce distinction between trashing (default) and permanent deletion (force), whether the operation is reversible, what permissions are required, or what happens to products assigned to the brand.

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?

It is a single short sentence with no padding, and the verb is front-loaded, so it is not verbose. However, the sentence is so minimal that it barely earns its place, delivering almost no information beyond the tool name.

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 destructive mutation tool with no annotations, no output schema, and an undocumented force parameter, the description is insufficient. An agent cannot determine whether the call removes a brand permanently or only trashes it, nor what it needs to pass for force.

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 only 50%: 'id' is documented as 'Brand ID' but 'force' has no description at all. The description does not compensate — it never mentions the force flag or explains what it toggles, leaving the most consequential parameter undocumented.

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 verb and resource ('Delete a WooCommerce product brand'), which is clearer than a bare restatement, but it adds essentially nothing beyond what the tool name wc_delete_product_brand already conveys. It does not differentiate this from sibling brand tools (wc_update_product_brand, wc_list_product_brands) or from the category/tag deletion tools.

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?

There is no when-to-use guidance, no statement of prerequisites or required capabilities, and no mention of alternatives or related tools. The agent is left to infer everything from the name alone.

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