etsy_get_listing

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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive, and the description adds no context beyond that — nothing about auth via api_key, rate limits, error behavior when an ID is invalid, or what the includes parameter changes. It doesn't contradict the annotations, but it contributes no behavioral signal of its own.

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?

A single front-loaded sentence with no filler; the resource and lookup key come first. It is efficient but so terse that it leaves useful space unused rather than being fully optimized.

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, and the description says nothing about what 'details' are returned or how includes (Images, Shop) expands the response. For a simple read tool with rich annotations this is adequate but leaves a real gap around return shape.

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 only 33%: includes has a schema description, but listing_id and api_key are undocumented. The description clarifies that listing_id is the lookup key, partially compensating, but it says nothing about api_key being a required credential, leaving the auth requirement for the agent to infer.

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?

States a specific verb (Get) and resource (a single Etsy listing) plus the lookup key (listing ID), which clearly separates it from etsy_search_listings and etsy_get_shop_listings. It doesn't name a sibling explicitly, so it stops just short of a 5.

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 phrase 'by listing ID' implies the tool should be used when a listing ID is already known (versus searching), but this is inferred rather than stated. No explicit when-not or alternative routing is given.

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