shopify_list_customers

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

The description states the tool is read-only, which is a key behavioral trait. However, it does not mention pagination behavior despite the 'limit' parameter, nor does it disclose potential rate limits or response structure. With no annotations provided, the description carries the full burden but only partially addresses it.

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 sentence that is clear and concise. No extraneous words. However, it could be slightly more structured by separating the read-only indication from the list of included fields. Still, it earns its place with efficiency.

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?

Given the lack of output schema, the description lists some return fields (orders count, amount spent) but omits other common details like pagination, total count, or default behavior. The tool is relatively simple with only two parameters, so the description is minimally adequate but not comprehensive.

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 50% (only 'query' has a description), and the tool description adds no parameter information beyond the schema. The 'limit' parameter lacks any explanation in either the schema or the description, and the description does not clarify how the parameters interact (e.g., pagination with query filtering).

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 it lists customers and includes orders count and amount spent. The verb 'list' and resource 'customers' are specific, and the read-only designation is helpful. However, it does not differentiate from sibling tools like shopify_customer_purchase_summary or shopify_inactive_customer_summary, which could cause ambiguity for an AI agent deciding which tool to use.

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 implies the tool is for listing customers, but it provides no explicit guidance on when to use it versus alternatives. Siblings include other customer-related tools (e.g., shopify_top_customers, shopify_customer_purchase_summary), and no when-not-to-use or alternative tool suggestions are given. The usage is implied but not clearly directed.

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