etsy_check_scopes

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

No annotations are provided, so the description carries the behavioral burden. It discloses that held=true asks Etsy what the token actually carries and requires a seller token, and it frames the tool as diagnostic. It doesn't spell out rate limits or response shape, but for a check-style tool this is solid context.

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?

Four short sentences, front-loaded with purpose, then when to use it, then how to use the parameters. Every sentence contributes to the diagnostic story with no filler.

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?

This is a simple tool with two optional parameters and no output schema. The description covers purpose, use cases, and both parameters well. It doesn't explicitly describe the response format, but the output is reasonably inferable from 'which scopes' and 'what each one unlocks.'

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 provides 100% parameter coverage, so the baseline is 3. The description's 'pass an operation id' and 'pass held=true' instructions reinforce the schema rather than adding new syntax or constraints. The 403-fix framing adds workflow context but no new parameter-level meaning.

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 opens by defining exactly what the tool delivers: which OAuth scopes the Etsy API needs and what each scope unlocks. This distinguishes it from sibling tools like etsy_call or etsy_list_operations, which are about executing or listing operations rather than explaining scope requirements.

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?

It gives explicit timing and diagnostic context: useful before authorizing an app and as the fastest way to understand a 403. It does not name sibling alternatives or state when not to use it, so it falls just short of the top anchor.

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