wordpress_wc_update_stock

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

With no annotations, the description carries the full burden of behavioral transparency. It merely says 'Update' without explaining how stock levels are changed, what value is used, whether it is idempotent, or if special permissions are needed. The schema only has productId, so it is unclear how the new stock level is specified.

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: a single, front-loaded sentence with no wasted words. It lacks structural elements like parameter details, but for the purpose of brevity it scores well.

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?

The tool is simple with only one parameter, but the description is too sparse. It does not explain the missing stock value parameter, return values, or when to prefer this over the more general product update tool. Given no annotations and no output schema, this incomplete description leaves critical gaps.

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% because the description does not mention any parameter. The only parameter 'productId' is self-explanatory from its name, but the description fails to compensate for the low coverage. More importantly, updating stock levels requires a stock quantity, yet no such parameter exists in the schema, making the tool's semantics confusing and incomplete.

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 ('Update') and the resource ('product inventory/stock levels'), conveying a specific purpose that is distinct from the broader sibling tool 'wordpress_wc_update_product'. However, it does not specify whether the update sets an absolute value or adjusts incrementally, leaving minor ambiguity.

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 no guidance on when to use this tool versus alternatives. It does not mention that this is specifically for stock levels while other product details should be handled by 'wordpress_wc_update_product', nor does it state any prerequisites like WooCommerce being active.

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