etsy_search_listings

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

With no annotations, the description carries full burden but only states 'Search active Etsy listings by keyword.' It does not disclose behavioral traits like pagination (via offset/limit), rate limits, authentication requirements, or the structure of search results.

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, short sentence, which is concise but too sparse for a tool with 10 parameters. It front-loads the core action but omits important supporting information, making it less useful than a slightly longer description would be.

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?

Despite having 10 input parameters, no output schema, and no annotations, the description provides almost no contextual information. It fails to explain what fields are returned, how sorting or filtering works, or basic usage patterns, leaving the agent to guess from parameter names alone.

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 approximately 50%, and the description adds no additional meaning to any parameters. For example, it does not explain how min_price/max_price work or the effect of taxonomy_id. The tool's search behavior is left implicit.

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 tool searches active Etsy listings by keyword, distinguishing it from siblings like etsy_get_listing or etsy_search_shops. However, it could be more precise about the scope (e.g., only active listings) and the exact resource type.

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 provided on when to use this tool versus alternative Etsy tools such as etsy_get_listing for specific IDs or etsy_search_shops. There is no mention of when not to use it or prerequisites like required permissions.

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