woo_push_serial

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

No annotations are present, so the description carries the behavioral burden. It discloses that the action is a create-or-update write operation, names the SKU pattern, and limits scope to one serial; it does not elaborate on confirmation semantics or side effects, but the key traits are 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 dense and front-loaded, with the core purpose first and then the decision rule. It is appropriately sized, though the trailing 'site: retail | dealer. confirm=true.' fragments are terse rather than fully structured.

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 three-parameter write tool with no output schema or annotations, the description covers purpose, scope, alternative, and all three parameters. It does not describe return values or confirm/false behavior, but it provides enough for a competent agent to invoke it correctly.

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 coverage is 0%, but the description compensates by defining serial_no (the serial appearing in SKU item_code::serial), enumerating site values as retail | dealer, and recommending confirm=true. It does not explain what confirm=false does or what the fields mean beyond these fragments.

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 verb ('Push'), a resource ('WooCommerce product for ONE firearm Serial No'), and the per-gun scope. It explicitly contrasts with woo_push_item, so an agent can distinguish the two listing 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?

Gives an explicit preference rule: use this over woo_push_item when only specific guns changed, and explains that woo_push_item pushes every Active serial. This is clear when-to-use and alternative guidance.

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