get-products

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

No annotations are present, so the description carries the full burden. It discloses the optional filtering behavior and provides query examples, and 'List' implies a read-only operation. However, it does not mention pagination, default limit behavior, or any potential side effects, leaving some behavioral traits unspecified.

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?

A single, front-loaded sentence states the main action first ('List products') and then the optional filter. It contains no redundant words and efficiently conveys the tool's primary purpose.

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 simple two-parameter list tool with fully described parameters, the description is largely adequate. It covers the operation and search behavior, but since there is no output schema or annotations, it does not explain return format or pagination details, which would make it fully complete.

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?

Input schema coverage is 100%, so the baseline is 3. The description adds value by giving a distinct extra example ('tag:sale') and clarifying that the query can be a title fragment, status, or tag, which goes slightly beyond the schema descriptions.

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 uses a specific verb 'List' with a clear resource 'products from the Shopify store', making it obvious this tool retrieves multiple products. This distinguishes it from siblings like get-product-by-id (single product) and update-product (mutation).

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 description does not say when to use this tool versus alternatives such as get-product-by-id, nor does it mention any exclusions or prerequisites. While 'List' implies a collection context, there is no explicit guidance on choosing between this and other product-related tools.

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