gold_wc_batch

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

With no annotations, the description carries the burden and does add useful behavioral context: it is a paid-only bulk mutation tool that can create, update, and delete up to 100 rows in one call. However, it does not mention the confirm=CONFIRM execution gate or possible partial-failure/destructive side effects beyond naming 'delete'.

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 core information is front-loaded: operation type, scope, and row limit appear first, followed by resource values and licensing. The 'CodeCanyon Advanced Bulk Edit $69 killer' marketing is mostly noise, but the overall description is still short 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?

For a complex bulk mutation tool with no output schema and no annotations, the description is not complete enough to invoke safely. It lacks object payload guidance for create/update, clarification that delete expects IDs, and explicit mention of the confirm gate, leaving the agent to infer critical execution details from the schema alone.

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 only 20%, and the description helps by pairing 'create', 'update', and 'delete' with the corresponding array parameters and listing the valid resource values. It also adds the 100-row limit. Still, it does not explain what should go inside the create/update objects or how delete IDs are expected to be formatted.

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 clearly states a specific bulk operation over products/orders/coupons/categories with create+update+delete and a 100-row cap. It goes beyond the name and implies a batch role distinct from single-entity siblings, though it does not explicitly contrast with the sibling bulk 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?

The phrase 'up to 100 rows in ONE call' implies use for bulk operations, and the resource list indicates scope. However, there is no explicit guidance on when to prefer this over sibling bulk tools like gold_wc_categories_bulk or gold_wc_coupons_bulk, nor any 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.