etsy_get_shop

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

With no annotations, the description carries the full burden of behavioral disclosure. It describes a read operation but does not specify returned fields, rate limits, authentication setup (api_key purpose), or any side effects. The minimal 'Get details' leaves significant behavioral ambiguity.

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 sentence, avoiding unnecessary words. However, it is too brief to be helpful, omitting critical details that would require expansion.

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 two parameters (one undocumented), no output schema, and sibling tools, the description is incomplete. It does not explain the output format, differentiate shop_id types, or reference related endpoints, leaving significant gaps for correct invocation.

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 50% (shop_id described). The tool description repeats that shop_id is a 'shop ID or numeric ID', adding no extra meaning. The api_key parameter has no guidance on origin or format, and the description fails to clarify that shop_id can accept both numeric and string (shop name) values.

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 verb 'Get details' and the resource 'Etsy shop', and specifies an identifier ('shop ID or numeric ID'). It distinguishes from sibling tools like 'etsy_search_shops' (which searches) and 'etsy_get_listings' (which gets listings), though it does not explicitly name them.

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 such as 'etsy_search_shops' or 'etsy_get_shop_listings'. It does not mention prerequisites, context, or scenarios where this tool is appropriate.

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