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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the bar is lower. The description adds genuine beyond-schema context: the tool only returns Replo-managed products, and the recommended user-facing action when the result is empty.

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?

Three short sentences with no filler, and the scope statement is front-loaded. Slightly redundant in restating 'products' twice, and it spends space on empty-state messaging while omitting pagination behavior.

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?

With no output schema, four zero-documented parameters, and pagination available via cursor/limit, the description should at least indicate the shape of the result (a list of products with a next cursor). Instead it covers only the data domain and an empty-state hint, leaving the calling contract underspecified.

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 0% across four parameters, and the description says nothing about projectId, query, limit, or cursor. An agent gets no hint that this is searchable or paginated (limit max 100, cursor-based), so the description fails to compensate for the undocumented schema.

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 ('Find') and resource ('Replo-managed products'), plus the use cases (catalog, product-page, checkout work). It also distinguishes the product set from Shopify-managed products, though it doesn't explicitly contrast with the singular get_product sibling.

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's exclusions are about data scope (not Shopify-managed products) rather than tool selection, so it doesn't say when to use this versus get_product, create_product, or update_product. The fallback instruction for empty results is helpful but is a post-call behavior, not a selection rule.

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