etsy_get_shop_info

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

With no annotations provided, the description carries the full burden of disclosing behavior. It indicates the tool is a get operation and lists some included data, but it does not mention whether authentication is required, whether the operation is fully read-only, how 'all listings' is returned or paginated, or any potential side effects.

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 focused sentence with no filler. Key information about the resource and the included data is front-loaded, though it could be slightly clearer about parameter requirements.

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?

The description is adequate for a simple get operation but incomplete in important ways: the schema marks both params optional while logically at least one shop identifier is needed, and the description does not address authentication or return structure. Since there is no output schema and no annotations, this leaves the agent with notable ambiguity.

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 input schema already has 100% coverage with descriptions for shop_url and shop_name, including the 'alternative to shop_name' note, so the schema handles parameter semantics. The tool description adds no extra parameter-level meaning beyond naming the shop resource.

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 uses a clear verb-resource structure: 'Get information about an Etsy shop' and specifies the content areas: ratings, policies, and all listings. It is clearly distinct from item-level or search tools, though it does not explicitly name a sibling alternative.

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 intended use is implied: call this when you need shop-level information such as ratings, policies, or listings. However, the description gives no explicit guidance on when to choose this over etsy_get_item_details or etsy_search_products, and it does not mention any prerequisites or exclusions.

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