Etsy MCP Server

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it's an OAuth 2.0 flow, opens a browser for user consent, and is required for authorization-dependent tools. It doesn't mention rate limits, error handling, or session duration, but covers the essential authentication behavior adequately.

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?

Perfectly concise with two sentences that each earn their place: first explains what the tool does, second explains when to use it. No wasted words and front-loaded with the core purpose.

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?

For an authentication tool with 0 parameters, no annotations, and no output schema, the description provides complete context about what it does and when to use it. It could mention what happens after authentication (e.g., token storage, session management) but covers the essential purpose and prerequisites well.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and instead focuses on the authentication process context.

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 specific action ('Authenticate with Etsy via OAuth 2.0'), the resource (Etsy platform), and the mechanism ('Opens a browser for consent'). It distinguishes itself from all sibling tools which perform various Etsy operations by being the authentication prerequisite.

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?

Explicitly states when to use ('Required before using tools that need user authorization') and provides clear context about its role as a prerequisite for other operations. It effectively distinguishes itself from all sibling tools that require authentication.

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