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

The annotations declare readOnlyHint=false, but the description repeatedly frames the operation as 'Filter,' 'searching,' and 'viewing' products, which are read-only actions. The description does not explain any side effects, permissions, rate limits, or why the tool is not read-only, creating a direct conflict with the annotation.

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 is front-loaded in the first sentence, and the trigger guidance follows logically. The trigger list is somewhat repetitive and the 'Even if the user does not mention the tool name' sentence is redundant, but the description is not bloated.

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?

This is a 16-parameter query tool with no output schema, so the description should clarify return format and pagination behavior. It covers use cases and filter dimensions, but it omits return details and does not resolve the readOnlyHint conflict; the rich schema carries most parameter detail.

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 16 parameters are already documented in the schema. The description lists the filterable dimensions but adds no syntax, defaults, or interpretation beyond what the schema provides, making 3 the correct baseline.

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 and resource: 'Filter Shopify standalone store products,' then lists the filter dimensions. The phrase 'standalone store products' distinguishes it from store-level sibling tools such as nexscope_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?

Provides explicit trigger phrases and says to invoke it even when the user does not mention the tool name, which gives clear usage context. However, it does not name alternatives or state when NOT to use it versus related product-query tools on other platforms.

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