etsy_shop

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

No annotations are provided, so the description carries the burden. It discloses the return payload fields and that it accepts id or name, but does not describe error behavior (e.g., not found) or any side effects. Given it's a read-only profile fetch, this is acceptable but not exhaustive.

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?

Two clear sentences, front-loaded with the main action, no redundant wording. Efficiently conveys purpose and input.

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 simple one-parameter GET operation with no output schema or annotations, the description adequately covers purpose, input, and key return fields. It lacks information on error states or when to prefer sibling search tools, but overall is sufficient for this simplicity.

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 coverage is 100% and the description's 'Accepts a numeric shop id or a shop name' simply restates the schema's description. No additional semantic value is added beyond the structured input schema.

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?

Description uses a specific verb+resource ('Get Etsy shop profile') and lists return fields (seller, headline, rating, sold count), clearly distinguishing from sibling tools like etsy_shop_listings or etsy_shop_reviews.

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?

Clearly implies this tool is for fetching a shop's profile when you have a numeric id or shop name. However, it does not explicitly mention alternatives or exclusions (e.g., use etsy_shop_search when only a query is available), so it falls short of full guidance.

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