shopify_top_customers

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

With no annotations, the description bears the burden of behavioral disclosure. It mentions the customerType filter but does not explain that date range is required, that the output is a list, or any other behaviors. It provides minimal context beyond the schematic defaults.

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, concise sentence of 12 words, which is efficient. However, it lacks structure such as bullet points or sections that could improve readability for an agent.

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 absence of an output schema and 0% parameter coverage, the description is incomplete. It does not explain return values, the role of the query parameter, or the effect of limit, leaving an agent without sufficient context for correct invocation.

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?

The description only mentions the customerType parameter indirectly ('optional new/returning filter'). With 0% schema description coverage, the description should document other parameters like sortBy, limit, and query, but it does not add meaning beyond the 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?

The description clearly states the tool returns top customers sorted by sales or volume, with an optional filter for new/returning customers. This distinguishes it from sibling tools like shopify_list_customers or shopify_customer_purchase_summary by focusing on ranking by performance metrics.

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 explicit guidance on when to use or alternatives is provided. However, the purpose is clear enough that an agent can infer it should be used when needing a ranked list of top customers by sales/volume, though comparative context with siblings is missing.

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