etsy_list_operations

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

With no annotations, the description carries the full disclosure burden. It communicates that this is a read-oriented browse operation, that it covers the entire seller-facing Etsy API, and that each entry exposes the OAuth scope needed — actionable context for handling 403s. Exact output shape and pagination are not stated, but the core behavior is clear.

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?

Three sentences with no filler: purpose is front-loaded, the seller-facing scoping sentence gives useful context, and the final sentence points to the consuming tool. Every sentence earns its place.

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 a single-optional-parameter catalog tool with no output schema, this is nearly complete: it explains what the tool returns conceptually, why OAuth scopes matter, and how to use the result with etsy_call. The only gap is finer output-shape or pagination detail, which is not essential for selecting and invoking it correctly.

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 schema already documents the single optional search parameter, so the baseline is 3. The description adds value by naming the fields it filters (id, path, tag, summary) and providing concrete examples ('listing', 'receipt', 'shipping'), going beyond what the schema alone provides.

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?

Opens with a concrete action and countable resource: 'Browse all 105 operations in the Etsy Open API v3.' It clearly positions the tool as the operation catalog and ties it to the next step, 'find an operation id for etsy_call,' which distinguishes it from siblings like etsy_list_listings, etsy_get_listing, or etsy_call itself.

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 says when to use it: 'Use this to find an operation id for etsy_call.' It also gives helpful search direction by id, path, tag, or summary. It does not enumerate when-not-to-use conditions or name alternative siblings for comparison, so it stops just short of full routing guidance.

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