woo_delist_serial

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

With no annotations provided, the description carries the transparency burden. It clearly discloses the two concrete mutations (Draft status + stock 0) and the immediate effect (hiding the gun from the shop). It does not discuss reversibility or edge cases, but the core behavioral impact is explicit.

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 two short sentences with no filler. The primary action and effect are front-loaded, and the trailing parameter hints are minimal but useful. Every part 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?

For a simple 3-parameter tool with one required field and no output schema, the description covers the operation, the target state, the immediate result, site options, and the confirmation requirement. It is slightly terse on serial_no semantics but sufficient 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%, so the description must compensate. It adds meaning for 'site' by enumerating allowed values and clarifies that 'confirm' should be true to take effect. The required 'serial_no' is implied by the tool name and opening phrase, but no explicit format or guidance is given.

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 a specific verb ('Set'), a precise resource ('ONE Serial No's WooCommerce product'), and the exact state change ('Draft + stock 0'). It also differentiates itself by emphasizing serial-level operation and immediate effect, distinguishing it from item-level siblings like woo_delist_item.

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 gives context by noting applicable sites ('retail | dealer') and requiring 'confirm=true', which implies the confirmation step before executing. However, it does not explicitly state when to prefer this tool over alternatives such as woo_delist_item, or when not to use it.

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