get_customers

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'fetch customers' and does not mention pagination, default page size, return format, or that it is a read-only operation. The schema provides parameter details, but the description lacks key behavioral context like how results are returned.

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, clear sentence that immediately conveys the tool's purpose. There is no redundant or filler content, making it appropriately concise and well-structured.

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 list tool with 5 optional parameters and no output schema or annotations, the description is adequate but incomplete. It covers the basic purpose but does not explain pagination behavior, default values, or what the response looks like. These gaps could confuse an agent deciding whether to use this tool.

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 input schema has 100% parameter description coverage, so the schema already documents all five parameters. The description adds no extra parameter semantics beyond mentioning 'optional filtering', so it does not go beyond the schema baseline.

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 fetches customers from the Shopify store, using the verb 'Fetch' and the resource 'customers'. It distinguishes from get_customer (singular) by pluralizing 'customers', but does not explicitly name the alternative or clarify that it returns a list.

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 phrase 'with optional filtering' implies this tool is suitable for fetching customers with filters, but it gives no explicit guidance on when to use this over get_customer (for a specific customer) or other list tools. No exclusions or alternatives are mentioned.

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