wordpress_wc_delete_product

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

No annotations, so description carries full burden. It only states 'Delete' but does not disclose whether deletion is permanent or moves to trash, nor any side effects or permissions. The 'force' parameter hints at different behavior but is unmentioned.

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?

Extremely concise at three words, no wasted text. However, brevity sacrifices valuable information that could be included without bloat.

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?

Given the simple tool (2 params, no output schema), the description is insufficient. It fails to clarify the critical 'force' parameter behavior, success/failure indications, or destructive nature beyond the verb.

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 and the description does not explain the two parameters (productId, force). Parameter names are somewhat self-evident but not explicit about what 'force' does (e.g., bypass trash). The agent must guess.

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 'Delete WooCommerce product', which clearly indicates the action and resource. However, it does not distinguish from other deletion tools like wordpress_delete_post, though the 'WooCommerce' qualifier narrows it down.

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?

No guidance on when to use this tool vs alternatives. Siblings include many delete tools (e.g., wordpress_delete_post, wordpress_delete_media) with no differentiation provided.

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