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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful non-annotation context about result scope (Replo-managed only) and empty-result behavior, but says nothing about pagination despite cursor/limit parameters, which is the main behavioral gap.

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, front-loaded with the core purpose, and the scope caveat and fallback are placed after it. The clause "for catalog, product-page, or checkout work" is somewhat generic, but overall there is little waste.

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 paginated read-only search with no output schema and four undocumented parameters, the description covers purpose and result scope but omits pagination semantics and any return-shape hints. An agent could invoke it, but might misuse limit/cursor or mis-handle the result set.

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% and the description never mentions any of the four parameters. It does not explain that projectId is required, nor what query matches against, nor how limit/cursor paginate, so it 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+resource ("Find Replo-managed products") and scopes it to catalog/product-page/checkout work. It also draws a clear boundary against products managed by Shopify or other integrations, which helps separate it from the get_product/create_product/update_product siblings, though it never names those siblings directly.

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?

Gives a clear usage context (catalog, product-page, checkout work) and an explicit fallback instruction when no Replo-managed products are found. It stops short of naming when to prefer get_product (single-item lookup) or create_product over this search, so alternatives are only implied.

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