woo_push_item

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

With no annotations, the description carries the burden and it does so meaningfully: it flags the operation as consequential, requires confirm=true, and explains the push granularity for firearm categories. It stops short of describing overwrite effects, permissions, or what happens on partial failure, so it is good but not exhaustive.

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?

Three terse sentences pack the action, branching behavior, alternative, and key flags with no filler. The main action is front-loaded, and every clause adds information an agent needs.

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 3-parameter mutation tool with no output schema, the description covers core behavior, branching logic, the alternative, and the safety flag. It leaves minor ambiguity around return values and the exact meaning of 'uniform-price firearms,' but nothing essential to deciding whether to call it is missing.

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%, but the description compensates by documenting valid site values ('retail | dealer') and the confirm requirement. item_code is still only implied by the phrase 'for an Item,' but for a required single parameter that is sufficient context.

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?

States a specific action ('Push (create or update)') and target ('WooCommerce product(s) for an Item'), and distinguishes the per-serial vs item-level behavior. It also names the relevant sibling (woo_push_serial) for the single-gun case, so an agent can tell this from related tools.

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?

Explicitly gives the alternative and selection condition: 'For ONE gun use woo_push_serial instead.' It also clarifies when the tool pushes per-serial versus item-level, and notes the site parameter accepts retail or dealer, giving enough context to choose correctly.

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