gold_etsy_update_listing

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

No annotations are provided, so the description carries the behavioral disclosure burden. It identifies the mutation scope and auth/business constraints (BYOK, paid Pro), but does not mention that a CONFIRM value is required, whether the update is partial or full, reversibility, or return behavior.

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 very short and front-loaded, with no fluff. However, the telegraphic 'BYOK. PAID ONLY PRO $29.' is cryptic and could reduce clarity for an agent.

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 mutation tool with 7 parameters, no annotations, and no output schema, the description is too thin: it does not clarify partial vs full updates, confirmed-execution semantics, errors/return values, or when sibling tools should be used instead.

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 14%, and while the description lists five updatable fields, it adds little beyond their property names. It omits listing_id and confirm from the pattern, and does not explain optional/partial update behavior or value format expectations, so it fails to compensate for the low schema coverage.

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 and resource ('Update an Etsy listing') and scopes the update to title/description/price/quantity/state. This clearly distinguishes it from siblings like gold_etsy_creat_listing or gold_etsy_update_variation_price_qty, even though those are not named.

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 prerequisites (BYOK, paid-only Pro/$29) but no guidance on when to choose this tool over alternatives such as update_variation_price_qty or cre_at_listing. There are no when/when-not conditions or exclusions.

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