etsy_listing_images_list

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

The description only states 'list all images', consistent with the readOnlyHint annotation, but adds no extra behavioral detail beyond the annotation. It does not disclose return format, pagination, auth needs, or any side effects.

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 a single, clear sentence with no extraneous information, making it concise and front-loaded.

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 the absence of an output schema, the description should indicate the return value structure (e.g., list of image objects). It also lacks details on potential pagination or ordering, leaving the agent underinformed.

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?

The input schema has 0% description coverage; the two parameters (shop_id, listing_id) are not explained in the description. While the parameter names are somewhat self-explanatory in context, the description adds no meaning beyond 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 'List all images for a listing' clearly states the verb (list) and resource (images for a listing), distinguishing it from siblings like etsy_listing_image_get (single image) and etsy_listing_image_delete.

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 provides no guidance on when to use this tool versus alternatives, such as when to list all images versus retrieving a single image via etsy_listing_image_get. It also lacks any prerequisites or conditions.

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