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 and the description's bar is lower. The description adds nothing beyond that — no note on data freshness, result caps, or how the open-world external dataset is sourced — which is a meaningful omission for a market-data query.

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 purpose clause is front-loaded and useful, but the second and third sentences are keyword-stuffed trigger lists with heavy internal repetition ('Shopify stores', 'standalone stores', 'shopify stores', 'Shopify store query') that restate the same signal four or five times. Roughly half the text does not earn its place.

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 15-parameter, zero-required, read-only query with no output schema, the description covers the filtering surface adequately but says nothing about what a result record contains, how pagination behaves beyond the schema's defaults, or what empty results mean. It is workable but leaves the agent guessing about return shape on a complex tool.

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 the baseline is 3. The enumerated dimensions (country, product count, ad count, monthly visits/orders) mostly mirror parameters, but 'social media followers' has no corresponding filter parameter (only a sortBy enum) and 'years since creation' is only loosely tied to the coded `year` values, so the description slightly overpromises relative to the schema.

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 opens with a specific verb+resource ('Filter Shopify standalone stores') and enumerates the filter dimensions, so the agent knows exactly what the tool searches. The 'standalone' qualifier implicitly separates it from the sibling nexscope_shopify_product_query, but the distinction is never made explicit and the closest sibling nexscope_data_eh_shopify_store_query is not addressed at all.

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?

Usage is conveyed only through a long trigger-phrase list ('Triggered when users mention Shopify stores...'), which tells the agent the topic area but not the decision rule. There is no statement of when NOT to use it, no prerequisites, and no routing to the sibling store/product or marketplace store-query tools, so the agent must infer selection from keywords alone.

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