woocommerce_update_coupon

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. While it identifies this as an update operation, it fails to specify whether it performs partial updates (PATCH) or full replacements, what happens to omitted fields, error handling for invalid coupon_ids, or the return value structure.

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 brief (two sentences) but includes unnecessary metadata ('[UNIFIED]') that adds no semantic value for tool selection. The structure is front-loaded with the action but could remove the tag for clarity.

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 high complexity (16 parameters, 0% schema coverage, no output schema, no annotations), the description is insufficient. It lacks critical details about parameter formats, authentication requirements, error scenarios, and response structures necessary for correct invocation.

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%, requiring the description to compensate significantly. While it mentions 'discount amount, restrictions, and expiration' mapping to some parameters, it fails to document the other 14 parameters including required fields (site, coupon_id), nor does it explain expected formats (e.g., date strings, comma-separated product IDs, boolean strings).

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 tool 'Update[s] an existing WooCommerce coupon' with specific examples of updatable fields (discount amount, restrictions, expiration). It implicitly distinguishes from sibling tools like woocommerce_create_coupon and woocommerce_delete_coupon by specifying 'existing' and 'update'.

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 lists what fields can be updated but provides no explicit guidance on when to use this tool versus alternatives (e.g., when to update vs. delete and recreate), nor does it mention prerequisites like requiring a valid coupon_id.

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