etsy_listings_search

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

Annotations already indicate readOnlyHint=true, so read-only nature is clear. The description adds no additional behavioral context such as pagination, rate limits, or result format, which would be helpful for a search tool with many filters.

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 and not verbose, but it is too brief to be informative. For a tool with 14 parameters, more detail is warranted.

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 complexity of the search (14 parameters, filters like color, price, location, sorting), the description is inadequate. It does not explain key features nor reference the rich set of filters. The lack of output schema also means return value info is absent.

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 29% (4 of 14 parameters have descriptions). The description mentions 'full filter support' but does not elaborate on any parameter meanings. With such low coverage, the description fails to compensate.

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 it searches all Etsy listings with full filter support. The verb 'search' and resource 'Etsy listings' are specific, and it distinguishes from sibling listing tools like get, list, or shop-specific searches.

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 on when to use this tool versus alternatives. There are many listing tools (e.g., etsy_listings_list, etsy_shop_listings_search) but the description does not explain what makes this search different or when to choose it.

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