etsy_listing_translation_get

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

The description is neutral and aligns with the readOnlyHint annotation, indicating no side effects. However, it adds no extra behavioral context beyond the annotation. Since annotations already cover safety, a score of 3 is appropriate.

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 wasted words. It is appropriately concise for a simple tool, though slightly lacking in detail for completeness.

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 no output schema and minimal description, the agent lacks information about return structure. The tool is simple, but the description does not hint at what the translation response contains or provide context for shop_id and listing_id. Adequate but not comprehensive.

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 low (33%), and the description adds no parameter details. Only the 'language' parameter has a schema description (ISO code). The description does not explain 'shop_id' or 'listing_id', which are critical but somewhat intuitive. It fails to compensate for the schema gap.

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 states the verb 'Get' and resource 'translation for a listing by language', clearly indicating a read operation for a specific translation. It distinguishes from sibling tools like 'etsy_listing_translation_create' and 'etsy_listing_translations_list' by focusing on retrieving one translation by language.

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?

No usage guidelines are provided. The description does not specify when to use this tool versus alternatives (e.g., listing translations list or create). The agent receives no guidance on context or exclusions.

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