Reihenfolge der Produktbilder ändern (Stufe 2)

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

No annotations are provided, so the description must disclose behavior. It covers dry_run preview, required confirmation, and non-re-upload. However, it does not mention permissions, reversibility, or what happens after confirm:true is executed.

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: the first states the purpose, the second adds critical usage warnings. No filler or redundant content.

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?

There is no output schema, but the description indicates what dry_run returns (comparison of current and planned order). Combined with the schema's parameter descriptions, this is adequate for correct selection and invocation. It could optionally mention how to obtain listing_image_id, but that is readily available via sibling tool etsy_get_listing_images.

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 75%, with dry_run and confirm already described in the schema. The description adds clarity about dry_run output (current vs. planned order) and the confirmation requirement, but provides no new meaning for the `order` array structure beyond what the schema specifies.

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's function: changing the display rank of already-uploaded listing images without re-uploading them. This distinguishes it from related tools like etsy_upload_listing_image and etsy_update_listing.

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?

It gives clear context: used when images already exist and need reordering, with dry_run preview and mandatory confirmation. It does not explicitly name alternative tools, but the phrase 'ohne sie neu hochzuladen' implies the alternative of re-uploading.

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