woo_bulk_update_stock

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no permissions required, no statement about whether the batch is atomic or how partial failures are handled, and no note on whether omitted stock_status/stock_quantity fields are left untouched. Only the word 'bulk' hints at multi-item semantics.

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 single four-word sentence is front-loaded and wastes nothing, but it is under-specified rather than truly concise—it omits details an agent needs for a mutation tool. Brevity here comes at the cost of completeness.

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 batch mutation tool with no annotations and no output schema, the description should at minimum state failure behavior, matching semantics, and any return/result expectations. None of that is present, leaving the agent to guess about a destructive stock-changing 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?

Schema description coverage is 100%, so the schema already documents 'site' (see list_sites) and the 'products' array with its id/stock_status/stock_quantity fields. The description adds no extra meaning about how the array is matched or validated, so the baseline 3 applies.

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?

Specific verb+resource: 'Bulk update product stock' tells the agent it is a batch mutation on stock data, which is clearly distinct from read-side tools like woo_stock_report. It stops short of naming any sibling (e.g. woo_update_product or woo_update_variation) that also touches stock fields, so differentiation is left to inference.

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?

There is no when-to-use guidance at all: nothing says when to prefer this batch tool over per-product updates via woo_update_product/woo_update_variation, nor are prerequisites (e.g. needing a site id) or exclusions stated. The description is purely a restatement of the operation.

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