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

Annotations declare readOnlyHint=false and openWorldHint=true, which is the only signal that this is not a pure read; the description's word 'Query' adds nothing and sits in mild tension with readOnlyHint=false (the schema's isStar=1 write-ish flag explains the non-read annotation, but the description never mentions it). Nothing is said about auth, rate limits, result size, or what the tool returns.

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?

It is very short and front-loaded, but the brevity is under-specification rather than economy: the single sentence duplicates the title verbatim and earns no place on its own.

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 24-parameter, open-world query tool with no output schema, the description leaves the agent without any explanation of result shape, pagination semantics (page/pageSize), or how the begin/end range pairs interact. It is essentially empty relative to the tool's complexity.

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 100%, so all 24 parameters (including the begin/end range pairs for sales, reviews, favorites, weekly metrics, and store-open dates) are already documented in the schema. The description adds no syntax, pairing rules, or defaults beyond it, which is the baseline 3 case.

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 only restates the title and name: 'Etsy Product Research: etsy/store Query API' names a resource and a query verb but adds no explanation of what is actually queried (store listings? store rankings? filters?). It does nothing to separate it from close siblings such as nexscope_etsy_store_query, nexscope_data_eh_etsy_product_query, or nexscope_data_eh_shopify_store_query.

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 when-to-use guidance, no prerequisites, no exclusions, and no named alternative. With this many near-identical Etsy/Shopify store and product query siblings, an agent has to guess entirely from the name which one to call.

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