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 adds value by explaining the effect of the 'force' parameter (permanent deletion vs. trash bypass), which is a key behavioral trait. However, it doesn't cover other aspects like permissions required, error conditions, or what the output schema might indicate, leaving gaps in transparency for a destructive operation.

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 two sentences that directly address the tool's purpose and key parameter behavior. It is front-loaded with the main action and wastes no words, making it efficient and easy to parse for an AI agent.

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 complexity (destructive operation with 2 parameters), no annotations, and an output schema present, the description is moderately complete. It covers the core action and a critical parameter, but for a deletion tool, it lacks details on permissions, error handling, or confirmation prompts, which could be important for safe usage. The output schema might fill some gaps, but the description itself has room for improvement.

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?

The schema description coverage is 0%, so the description must compensate. It adds meaningful semantics by explaining the 'force' parameter's effect ('permanent deletion (bypass trash)'), which clarifies beyond the schema's boolean type. The 'product_id' is implied but not detailed, but with only 2 parameters and one well-explained, this provides good compensation, though not exhaustive.

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 clearly states the action ('Delete') and resource ('a product'), making the purpose specific and understandable. It distinguishes from sibling tools like 'update_product' or 'get_product' by focusing on deletion. However, it doesn't explicitly differentiate from 'delete_coupon' or 'delete_webhook' beyond the resource name, which is implied but not stated.

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?

The description provides some guidance by mentioning 'Set force=True for permanent deletion (bypass trash)', which implies an alternative behavior (non-permanent deletion) and a context for using the force parameter. However, it lacks explicit when-to-use vs. alternatives (e.g., compared to other deletion tools or update operations) and doesn't specify prerequisites or exclusions, leaving usage somewhat implied.

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