etsy_listing_translations_list

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

The annotations already declare readOnlyHint=true, so the description does not need to restate that. However, it adds no further behavioral context, such as whether the output is paginated or what happens if no translations exist. This is acceptable but minimal, scoring 3.

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 sentence with no wasted words. However, it is slightly too terse, missing the opportunity to include parameter hints or context that would not compromise brevity. It earns a 4 for being efficient but borderline under-specified.

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 tool's simplicity (list translations) and lack of output schema, the description should at least imply that the result is a list of translation objects. It does not clarify the relationship to sibling tools like translation_get, nor does it mention the need for shop_id and listing_id. This inadequacy results in a low completeness score.

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 schema has 0% description coverage and the description does not elaborate on the required parameters (shop_id, listing_id). While 'for a listing' hints at listing_id, shop_id is left unexplained, leaving ambiguity. The description adds insufficient meaning beyond the raw 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 clearly states the action ('List') and the resource ('all translations for a listing'). It effectively distinguishes itself from sibling tools like etsy_listing_translation_create, etsy_listing_translation_get, and etsy_listing_translation_update by specifying that it returns all translations.

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 over its siblings (e.g., etsy_listing_translation_get). It does not mention scenarios or criteria that would lead an agent to choose this tool over alternatives.

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