Preis eines Listings ändern (Stufe 2)

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

With no annotations provided, the description carries the transparency burden. It discloses the dry_run default preview behavior (alt→neu), the mandatory confirmation requirement (confirm:true after explicit user consent), and the fact that the tool changes prices. Minor ambiguity: 'IMMER' might be overstated since confirm is only needed for dry_run:false, but it still adds useful context.

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 two sentences, front-loaded with the core purpose, and covers both modes, confirmation workflow, and dry_run behavior without any redundant words. Highly concise and well-structured.

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?

The description adequately covers the main workflow: two pricing modes, dry_run preview, and confirmation requirement. However, it does not explicitly state that price and variation_prices are mutually exclusive, and the 'immer' claim for confirmation could mislead. Minor gaps but overall effective for a moderately complex tool.

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 100% with detailed parameter descriptions (price, confirm, dry_run, variation_prices, listing_id). The tool description adds little beyond what the schema already specifies, so the baseline of 3 is appropriate.

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 the tool changes the price of a listing ('Ändert den Preis eines Listings') and distinguishes two modes: uniform or per-variant. This is specific enough to differentiate from sibling tools like etsy_update_inventory or etsy_update_tags.

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 the tool is for price changes and explains the two modes, but it does not explicitly state when to use this tool versus alternatives like etsy_update_inventory or etsy_update_variations. No exclusions or alternative tool references are given.

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