etsy_get_listing

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

The description discloses that the endpoint is public and does not require a seller token, which is valuable behavioral context. But with no annotations, it does not explicitly state whether the operation is read-only, mention rate limits, errors, or describe the response behavior beyond 'in full'.

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 extremely concise—two short phrases with no fluff—and front-loads the core purpose before the access note. It is a bit telegraphic, but every part earns its place.

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?

For a simple fetch-by-ID tool, the description covers the core purpose and public access, and the schema documents the optional 'includes' parameter. However, it lacks explicit usage guidance, response expectations, and any note about how 'includes' affects the returned detail, leaving moderate gaps.

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 50%: 'includes' is described in the schema, but 'listing_id' has only a type. The description adds no parameter-level meaning and does not compensate for the undocumented required parameter.

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 'One listing in full' clearly identifies the resource (a single listing) and the scope ('in full'), which distinguishes it from etsy_list_listings. It lacks an explicit verb like 'retrieve' or 'get', but the meaning is unambiguous from the name and phrasing.

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 implies usage for fetching one complete listing rather than a list, and the note 'Public — works without a seller token' gives useful context. However, it does not explicitly state when to use this tool versus alternatives like etsy_list_listings or etsy_call.

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