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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no indication of pagination limits, result volume, or that the many begin/end pairs are range filters that must be supplied in pairs.

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 short, but that brevity reflects under-specification rather than economy — the single sentence is pure title echo and no part of it earns its place by adding information.

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 store-research endpoint with no output schema, the description should at minimum say what a result row represents (store with sales, reviews, favorites, weekly deltas) and how the range parameters combine. None of that is present, leaving the agent to reverse-engineer intent from parameter names alone.

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 and sortBy/sortDesc codes) are documented in the schema itself. Per the baseline rule, a 3 is appropriate; the description contributes no additional parameter meaning.

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 is a restatement of the title: 'Etsy Product Research: etsy/store Query API' names no specific verb or scope beyond what the name already conveys. It does not distinguish this from nexscope_etsy_store_query, nexscope_data_eh_etsy_product_query, or nexscope_data_eh_shopify_store_query, all of which are near-identical siblings.

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 at all — no mention of what a store query is for, when to pick it over the product query sibling, or what filters are required to make it useful. An agent must infer everything 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.