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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description adds only the page limit (1–50) and does not explain pagination behavior, cursor semantics, detail/summary modes, or source fallback behavior. That is a thin addition for a 14-parameter listing tool.

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 a single front-loaded sentence with no wasted words. Its brevity is appropriate in form, though it is too terse to carry the needed semantics for a tool of this complexity.

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 14 parameters, four enums, a nested shopify_connection union, no output schema, and zero schema descriptions, the description is far too sparse. It does not explain the primary routing parameter (kind) or how the many filters and pagination controls compose.

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 14 parameters, so the description must compensate—and it largely does not. It mentions the page limit range, but does not explain kind (the central enum), refs, query, cursor, detail, source, status, currency, collection, or the shopify_connection oneOf structure.

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 states a clear read operation and enumerates the catalog resources covered (products/variants/prices, stock, collections/categories/tags/discounts). This distinguishes it from mutating siblings like catalog_update and catalog_import. It is not fully precise about the kind-based listing model, but the verb+resource is clear.

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?

It gives no guidance on when to use this versus catalog_update, catalog_import, or other list tools. It does not mention that 'kind' selects the resource family or how pagination cursors should be used. Only the page limit is stated.

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