woocommerce_update_product

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

No annotations provided, yet description omits critical behavioral details: it's a partial update (null values = no change), mutation risks, authentication requirements, or error scenarios (e.g., product not found).

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?

Two sentences, front-loaded with action. Efficient length though '[UNIFIED]' tag adds no value. Every substantive word earns its place.

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?

Complex mutation tool with 15 parameters, no annotations, and no output schema. Description lacks return value documentation, error handling, rate limits, or confirmation that this performs partial updates (PATCH-like behavior) rather than full replacement.

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. Description lists ~8 of 15 fields (name, slug, pricing, etc.) providing some semantic value, but fails to document required params ('site' format unclear, 'product_id' semantics undefined) or explain that null defaults mean 'no change'.

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?

Clear verb ('Update') + resource ('WooCommerce product') with 'existing' qualifier distinguishing from sibling 'woocommerce_create_product'. Lists updatable fields. '[UNIFIED]' prefix is noise but doesn't obscure purpose.

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 vs 'woocommerce_create_product' or prerequisite steps (e.g., obtaining product_id via list_products). No mention of partial update semantics.

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