WooCommerce MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action (delete) but doesn't cover critical aspects like permissions required, whether deletion is permanent or reversible, confirmation prompts, or error handling. The 'force' parameter hints at optional behavior, but this isn't explained.

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?

The description is extremely concise with a single sentence, 'Delete a webhook.', which is front-loaded and wastes no words. However, this brevity comes at the cost of completeness.

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 tool's destructive nature (delete), no annotations, 0% schema coverage, and an output schema (which isn't described), the description is inadequate. It lacks essential context like behavioral traits, parameter meanings, and usage guidelines, making it incomplete for safe and effective use.

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 the description must compensate but adds no parameter information. It doesn't explain what 'webhook_id' is, how to obtain it, or what the 'force' parameter does (e.g., bypasses confirmation). This leaves both parameters undocumented beyond their schema types.

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 'Delete a webhook' clearly states the action (delete) and resource (webhook), but it's overly generic and doesn't differentiate from sibling tools like delete_coupon or delete_product. It lacks specificity about what a webhook is in this context.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing webhook ID), when not to use it, or how it relates to sibling tools like create_webhook or list_webhooks.

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