gold_etsy_update_variation_price_qty

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

With no annotations, the description carries the behavioral disclosure burden. It usefully signals a bulk mutation action, brings your own key (BYOK), and a paid-only restriction. However, it does not mention the CONFIRM gate, irreversibility, or any operational side effects beyond updating prices and quantities.

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 short and front-loads the key action, but it includes promotional fluff—'sthe variant bulk edit eRank never built'—that does not help an agent. BYOK and PAID ONLY PRO are useful but telegraphic and unexplained.

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 a mutation-oriented bulk operation with no annotations and no output schema, the description omits important invocation context: the required CONFIRM value, how products should be matched by sku, and what happens on partial failures. An agent can probably choose the tool but not confidently execute it from the description 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 33%, so the description must compensate. It partially does: 'one listing' clarifies listing_id and 'price/qty per product offering' clarifies the products array's intent. But confirm is not explained in the description, and sku matching semantics are left entirely to the schema.

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 and resource: 'Bulk-update variation offerings (price/qty per product offering) on one listing.' This clearly distinguishes it from generic listing tools like gold_etsy_update_listing or gold_etsy_get_inventory by narrowing to variation-level price and quantity updates.

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 description implies its purpose: use it when you need to update variation prices or quantities on a single listing. However, it offers no explicit guidance on when not to use it or which sibling tool to prefer for adjacent tasks, such as updating non-variation listing fields.

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