etsy_search_shops

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and repeatability are covered. The description adds only that matching is by name; it says nothing about pagination behavior (limit/offset exist), result caps, or ordering — context the annotations do not supply but which matters here.

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?

A single short sentence that is front-loaded and zero-waste, but its brevity comes from omission rather than precision — key call-shaping information is simply absent.

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?

With four parameters, no output schema, and undocumented pagination and auth parameters, the description leaves too much unstated for an agent to call this correctly on the first try — particularly how many results come back and how to page through them.

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 25%: only shop_name is documented, and the description merely restates it. The limit and offset parameters have no type, range, default, or maximum guidance anywhere, and api_key is undocumented — the description does nothing to close that gap.

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?

States a specific verb+resource ('Search for Etsy shops') and the search key ('by name'), which separates it from etsy_get_shop (lookup by ID) and etsy_search_listings (different resource). It stops short of describing what a match or result set looks like, so it is clear but not maximally informative.

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?

There is no guidance on when to use this versus etsy_get_shop or etsy_search_listings, no mention of whether the search is fuzzy or exact, and no prerequisites beyond the implicit api_key parameter. The agent must infer the routing decision entirely from the tool name.

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