shopify_search_suggest

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

With no annotations, the description carries the transparency burden. It discloses the endpoint is credential-free and uses Ajax, indicating no authentication needed. However, it lacks details on rate limits, error handling, or data freshness, which are typical for such tools.

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 description is extremely concise at one sentence, covering the primary purpose, return types, and source. It is front-loaded with the action verb 'Get' and avoids unnecessary details.

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?

Given no output schema, the description should explain what the return object looks like. It mentions the return types but not the structure. The parameter documentation in the schema covers the inputs, but overall completeness for a tool with 4 parameters and no annotations is adequate but not fully comprehensive.

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 coverage is 100%, so the baseline is 3. The description does not add new semantics beyond the schema; it mentions return types but does not elaborate on parameter syntax or constraints beyond what the schema provides.

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 clearly states the tool retrieves Shopify search suggestions, listing the specific return types (products, collections, query suggestions) and noting the endpoint is credential-free and uses predictive search Ajax. This distinguishes it from other Shopify search tools like shopify_search and similar suggest tools.

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 implies use for autocomplete-like suggestions but does not explicitly state when to use this tool versus alternatives like shopify_search or other suggest tools. No exclusions or best practices are provided.

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