woo_delist_item

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

With no annotations, the description carries the full burden, and it does well by stating the exact state change ('Draft + stock 0') and the immediate commercial effect. It also surfaces the confirm=true requirement. It stops short of describing reversibility or what happens when confirm is false, but the core mutation is clearly disclosed.

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 short sentences carry the action, the effect, and critical parameter constraints with no filler. The main behavior is front-loaded, and the inline 'site: retail | dealer. confirm=true.' is economical and scannable.

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 a no-annotation mutation with no output schema, so more context would help. The description covers the action and key parameter values, but it omits explicit distinction from the similar woo_delist_serial tool, possible side effects, and response/return behavior. Adequate for invoking, but not fully complete.

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 useful semantics for site ('retail | dealer') and instructs confirm=true, but it does not describe item_code, which is the only required parameter, nor explain the meaning of confirm=false beyond the schema's default.

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 opens with a specific verb and resource: 'Set the WooCommerce product for an Item to Draft + stock 0'. It clearly states the resulting outcome ('hiding it from the shop immediately') and distinguishes this item-level delist tool from serial-level siblings like woo_delist_serial.

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 usage context is only implied: this is the tool to use when an Item should no longer be visible in the shop. It does not explicitly state when to choose this over woo_delist_serial or when not to use it, such as when only a serial needs delisting.

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