dispose_web_order

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds useful traits: no ShipStation push, idempotency per {serial, order}, and the confirm=true requirement. Still, it never explains what 'dispose' actually does to inventory/records or whether the operation is reversible, leaving the core destructive semantics unclear.

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 three tight sentences with no filler. It front-loads the action and quickly adds the critical caveat, idempotency note, and confirmation requirement. Every sentence 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?

This is a destructive, mutation-style tool with no annotations and no output schema, so the description needed to cover more ground. It explains the order type and the no-ShipStation side effect, but it does not define the format of woo_online_order, what happens when confirm is false, or what a successful disposal returns. These are material gaps for an agent deciding whether and how to invoke it.

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 needed to add meaning for both parameters. It only advises confirm=true and references an ambiguous {serial, order} idempotency key; the main parameter woo_online_order is not given a format, source, or example. The mention of 'serial' does not match any input field, which adds confusion rather than clarification.

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 ('Dispose') and a precise resource ('firearms on a paid Woo Online Order (web row)'). It also explicitly distinguishes this tool from ShipStation-handled orders with 'No ShipStation push here,' which differentiates it from related dispose/shipping 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?

It clearly identifies the target scenario: a paid Woo Online Order that is shipped by the store's own WooCommerce plugin. However, it does not explicitly name an alternative sibling tool or provide an overt 'use dispose_order instead' rule, so it has solid context but no formal when-not-to-use guidance.

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