etsy_list_listings

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that listings are filtered by state, which largely repeats the schema. It does not disclose pagination behavior, default state behavior, response shape, or any authorization requirements.

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 short, front-loaded phrase with no filler or redundant detail. However, it is a fragment rather than a full sentence, and the extreme brevity starts to undermine 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 four parameters, no output schema, and no annotations, this description is under-specified. An agent cannot tell what happens when state is omitted, how pagination works, what fields are returned, or what errors may occur.

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 description coverage is only 25%, and the description does not compensate. It hints at shop_id ('in a shop') and state ('filtered by state'), but says nothing about limit or offset semantics, defaults, or how the state filter behaves when omitted.

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 identifies the resource ('listings'), the scope ('in a shop'), and the key filter ('by state'). It is clear enough to distinguish from etsy_get_listing (single listing) and etsy_list_receipts (receipts), though it does not name those siblings explicitly.

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?

There is no guidance on when to choose this tool versus etsy_get_listing, etsy_list_receipts, or etsy_list_operations. The context is implied only by the resource name, with no explicit when to use or when not to use.

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