etsy_get_shop_listings

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

There are no annotations, so the description must disclose behavior. It only says 'Get active listings' without explaining authentication needs (api_key), pagination limits, sorting behavior, or what happens if the shop has zero active listings. The description is insufficient for a tool with no annotations.

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 fluff, but it is overly terse. Conciseness is good, but structure could be improved by adding a brief note on common parameters or behavior without sacrificing brevity.

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 has 6 parameters, no output schema, and no annotations, the description lacks completeness. It does not cover pagination (limit/offset), sorting (sort_on/order), or return expectations. Compared to more complete sibling descriptions, this one is sparse.

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 input schema has 6 parameters with 0% schema description coverage (no descriptions in the schema). The tool description does not mention any parameters or provide context for them (e.g., defaults for limit/offset, allowed sort_on values). This forces the agent to infer meaning from parameter names alone.

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 verb 'Get', the resource 'active listings', and the context 'for an Etsy shop'. It distinguishes from sibling tools like etsy_get_listing (single listing) and etsy_search_listings (cross-shop search), making the purpose unambiguous.

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 guidance is provided. The description does not indicate when to use this tool versus alternatives (e.g., etsy_search_listings), nor does it mention prerequisites like requiring a valid shop_id or how pagination works.

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