etsy_get_shop_listings

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds the useful 'active' scoping but says nothing about pagination, rate limits, or authentication requirements. With annotations carrying the safety burden, this is a modest but real value add.

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 single sentence is front-loaded and free of waste. However, it is arguably too terse for the parameter surface it needs to support, which slightly undercuts the benefit of its conciseness.

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 six undocumented parameters, no output schema, and only safety annotations, the description is incomplete. It should explain pagination, sorting options, and the authentication requirement to be sufficient for correct invocation.

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 0% for six parameters, and the description only implies shop_id via 'Etsy shop'. It does not clarify limit, offset, sort_on, sort_order, or the required api_key, leaving the schema to speak for itself in a context where it cannot.

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 a specific verb and resource ('Get active listings for an Etsy shop'), clearly distinguishing it from single-listing or shop-detail siblings. It does not explicitly contrast with etsy_search_listings, so a 4 rather than 5 is appropriate.

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 guidance is given on when to use this tool versus alternatives like etsy_search_listings or etsy_get_listing. The implied use case (get listings for a known shop) is present, but there are no exclusions or alternative routing.

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