woo_push_item

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

No annotations provided; description discloses consequential nature (confirm=true) and per-serial behavior. Lacks details on error handling, auth needs, or rate limits, but is reasonable for a mutation tool.

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 sentences, mostly concise. The second sentence is dense but carries necessary logic. Could be slightly restructured for clarity.

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?

Given no output schema, no annotations, and 2 params, the description covers core behavior and key parameter semantics. Missing return values, error states, and permissions, leaving some gaps.

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%; description adds meaning for the confirm parameter (consequential). However, item_code parameter lacks any format or constraint guidance, leaving a gap.

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?

Description clearly states the tool creates or updates WooCommerce products for an Item, and explains behavior differentiation per item type (per-serial vs single product). This distinguishes it from siblings like woo_delist_item and woo_reconcile.

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?

Implies usage through context (consequential, confirm parameter), but lacks explicit guidance on when to use this tool versus alternatives. No mention of when not to use or prerequisites.

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