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

Annotations supply only readOnlyHint=false and openWorldHint=true, so the description must carry the behavioral load. It says nothing about data freshness, result caps, rate limits, pagination behavior, or cost, and its 'filter' framing reads as a pure read query while the annotations mark it non-read-only — an unresolved tension the description never explains.

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 first sentence is well-formed and front-loaded, but the remaining two sentences are heavy repetition of trigger phrases ('Shopify stores', 'standalone stores', 'shopify stores') with almost no new information. Roughly half the text is redundant keyword padding.

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 15 optional parameters, no required fields, no output schema, and range-pair parameters (min/max) plus paging and sorting controls, an agent needs guidance on defaults and combinations that the description never provides. It also omits any indication of what a result record contains.

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 baseline is 3. The description does add a light mapping of business concepts to parameters (store name/domain, country, years since creation, product/ad/visit/order counts), though it also mentions social media followers as a filter dimension that only exists as a sort field, which could mildly mislead.

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 opening sentence gives a specific verb (filter) and resource (Shopify standalone stores) and enumerates the filterable dimensions, which lets an agent distinguish it from nexscope_shopify_product_query. It does not, however, acknowledge the near-identical sibling nexscope_data_eh_shopify_store_query, so sibling differentiation is incomplete.

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 trigger keyword list implies when to use it (store search, filtering store data, performance analysis), but it is keyword enumeration rather than guidance. There are no exclusions and no comparison to the other *_store_query tools (Etsy, Temu, the data_eh Shopify variant), so an agent still cannot tell when to prefer this over them.

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