list_customers

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

No annotations are present, so the description bears full responsibility. It states the action and a requirement, but omits important behavioral details such as whether the operation is read-only, any rate limits, pagination behavior, or response structure. The environment variable note adds some transparency, but overall insufficient.

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 concise with two sentences, front-loading the primary action. While it lacks depth, it wastes no words and is well-structured for immediate understanding.

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 annotations, the description should cover return format, pagination, and filtering behavior. It only states the purpose and an environment variable, leaving the agent to infer most runtime context from the parameter schema alone. With many sibling tools, no guidance on differentiation further reduces completeness.

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 coverage is 100%, with both parameters (limit, offset) fully described via their schema properties. The description adds no additional meaning beyond the schema, meeting the baseline expectation but providing no extra value.

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?

Description uses a specific verb 'List' and identifies the resource as 'customers who have placed orders in your Karrito store', which clearly distinguishes it from sibling tools like list_shipping_options or get_customer.

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?

Mentions a prerequisite (KARRITO_API_KEY) but provides no guidance on when to use this tool versus alternatives like get_customer, nor any scenario exclusions. The usage context is implied as basic listing, but not explicitly clarified.

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