shopify_products

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

No annotations exist, so the description carries the full burden and fails to: state that authentication credentials are required, describe pagination or what 'limit' defaults to, or say whether results are a flat list or paged envelope. 'Get' at least implies a read-only operation, but nothing about rate limits, error behavior, or result shape is disclosed.

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?

One short, front-loaded sentence with no padding, which is structurally sound. However, it is concise to the point of under-specification — the brevity comes from omitting information rather than from tight writing.

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 seven optional parameters, no annotations, no output schema, and no parameter documentation, the agent cannot tell how to authenticate, whether shop_domain needs a full URL or hostname, or how to page results. For a credentialed third-party commerce API this description is materially incomplete.

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 seven parameters, including non-obvious ones: which credential field is actually required (api_key vs access_token), how collection_id and vendor/product_type interact, and what limit's default and maximum are. The description supplies zero parameter meaning, leaving every filter undocumented in both places.

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 ('Get') and resource ('products') scoped to a Shopify store, which cleanly separates it from shopify_orders, shopify_customers, shopify_collections and shopify_inventory. It stops short of saying whether this is a full listing or a filtered search, and gives no hint of how it differs from cross-platform siblings like woo_products or ls_list_products.

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?

No statement of when to call this versus shopify_collections (browse a curated set) or shopify_inventory (stock levels), and no mention of the auth prerequisites implied by the api_key/access_token/shop_domain parameters. The agent is left to infer everything from the name.

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