search_products

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

No annotations are provided, so the description carries the full burden for behavioral transparency. It states that only identity and total inventory are returned, but it does not explicitly mention whether the operation is read-only or if there are other side effects, auth requirements, or rate limits.

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 concise, using three focused sentences. It front-loads the primary purpose, then clarifies output limitations and usage context without unnecessary detail.

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 the description is sufficient for invocation, including query syntax and response scope. However, no output schema is provided and the description only names 'identity and total inventory' without specifying exact fields, leaving some minor ambiguity about the return shape.

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?

The description adds meaningful detail to both parameters: query is explained with Shopify search syntax examples, and limit's range is reiterated in the description. Schema coverage is 100%, and the description enhances understanding of how to construct effective queries.

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's purpose: searching/finding products by free text, vendor, or status. It distinguishes this from get_product by noting that this is the entry point when the handle is unknown.

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 explicitly says to use this tool first when you do not already know a handle, and directs users to get_product for per-variant detail. This provides clear when-to-use and alternative guidance relative to sibling tools.

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