搜索商品

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

Annotations already declare read-only, idempotent, and non-destructive behavior, lowering the burden on the description. The description adds that results are paginated but does not explain cursor semantics, result shape, or iteration behavior with the `after` parameter.

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 compact sentence states the operation, the query grammar, and the pagination behavior with no filler. It is front-loaded and easy to parse.

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?

The tool is simple and read-only, and the description covers the basic operation, but it leaves out how pagination is driven by `after`, and with no output schema it does not describe what the returned product objects contain. These are meaningful gaps for an agent, though not fatal.

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 only 33%, so the description must compensate. It clarifies that `query` uses Shopify search syntax, but it does not explain `after` (pagination cursor) or `first` (page size) beyond what the schema already gives.

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 ('query') and resource ('products'), and adds that it uses Shopify search syntax and returns paginated results. It clearly signals a search/list operation, but it does not explicitly contrast itself with shopify_get_product for single-product lookups.

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 guidance on when to prefer this tool over sibling tools, such as using shopify_get_product for a known product ID. The intended use is only implied by the search phrasing and pagination mention, not stated.

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