Etsy MCP Server

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

No annotations are provided, so the description carries the full burden. It mentions 'active' listings, implying a filter, but doesn't disclose key behavioral traits: whether authentication is required, rate limits, pagination behavior beyond the offset parameter, what the output format looks like, or error conditions. For a search tool with no annotation coverage, this leaves significant gaps.

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, efficient sentence that front-loads the core purpose. Every word earns its place: 'Search' (action), 'active Etsy listings' (resource), 'with keywords and filters' (scope). There is no wasted verbiage or redundancy.

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 (8 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose clearly but lacks behavioral context, usage guidelines, and output details. For a search tool with rich parameters but no structured safety or output information, it should do more to compensate, though the concise purpose statement meets a basic threshold.

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 100%, so the schema already documents all 8 parameters thoroughly with descriptions and enums. The description adds no additional parameter semantics beyond implying that filters are available. It doesn't explain parameter interactions, default values, or constraints beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('Search') and resource ('active Etsy listings'), and specifies the scope with 'with keywords and filters'. It distinguishes from siblings like 'get_listing' (single listing) and 'get_listings_by_shop' (shop-specific), but doesn't explicitly differentiate from potential search alternatives. The purpose is specific and actionable.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication), compare with siblings like 'find_shops' (which might search shops instead of listings), or indicate when other tools might be more appropriate. Usage is implied by the name but not explicitly stated.

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