wordpress_wc_update_stock

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

No annotations exist, so the description must fully disclose behavior. It fails to mention whether the operation is absolute or incremental, permissions needed, or error handling (e.g., product not found). The description is insufficient for a mutation tool.

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 concise at 4 words, but this is at the expense of clarity and completeness. It is front-loaded but too minimal to be effective.

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 (single input, no output schema), the description is extremely bare. It lacks essential details like the effect on existing stock, expected input format, and whether it works for variable products. The description is inadequate for an inventory update operation.

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?

With 0% schema description coverage, the description must explain parameters. It only names 'product inventory/stock levels' but does not elaborate on 'productId' (e.g., where to find it, data type constraints). The schema shows a number parameter but no added meaning.

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 'Update product inventory/stock levels', which is a clear verb+resource. However, it is vague about the exact operation (absolute set vs. increment/decrement) and does not distinguish from sibling tools like wordpress_wc_update_product that may also modify stock.

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 on when to use this tool vs alternatives (e.g., wordpress_wc_update_product for broader updates). There are no prerequisites, exclusions, or context on appropriate usage.

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