Delete a WooCommerce coupon by site and coupon ID to remove unwanted or expired discount codes from your store.
Delete a coupon
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Coupon ID | |
| site | Yes | Site id (see list_sites) |
Changes observed during successful MCP inspections.
v3.4.0Input schema / properties / siteAdded value: +{
+ "description": "Site id (see list_sites)",
+ "type": "string"
+}Input schema / requiredPrevious value: -[
- "id"
-]New value: +[
+ "site",
+ "id"
+]v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It implies a destructive mutation but says nothing about irreversibility, required permissions, side effects, or confirmation requirements.
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, but it is under-specified rather than efficiently informative. It is front-loaded and has no wasted words, yet the lack of any contextual detail makes it feel incomplete for a destructive operation.
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 tool with no annotations and no output schema, the description is too sparse. It does not mention the required site context (even though schema covers it), nor does it disclose behavioral expectations like return behavior or safety considerations.
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 100%, so the input schema already fully documents both parameters (id and site). The description adds no additional meaning beyond what the schema provides, which is the expected baseline when schema coverage is high.
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 specific verb and resource: 'Delete a coupon'. It clearly identifies the operation, but does not differentiate itself from sibling coupon operations like woo_update_coupon or woo_get_coupon beyond the verb.
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 about when to use this tool versus alternatives, nor are prerequisites or warnings mentioned. The operation is implicitly clear from the name, but there is no explicit usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.