wafle_customers_list

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

Annotations already cover read-only and idempotent behavior. The description adds useful architectural context that customers are derived from orders. However, it mentions 'has-orders' as a filter, which is not present in the input schema, potentially misleading the agent.

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?

Two succinct sentences; the first conveys the primary function and filters, the second provides essential architectural context. No wasted words.

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?

The description covers core functionality, filters, pagination, and an important data-model insight. It does not describe return format or sort order, but for a straightforward list tool with good schema coverage, this is acceptable.

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 80%, but the description adds meaning for the 'search' parameter ('by email/name') and clarifies the derived-data concept. The 'has-orders' mention is problematic since it is not a schema parameter, and page/per_page details are left to 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 explicitly states 'List customers of a store with pagination + filters' and lists specific filter types ('search by email/name, has-orders, segment'), distinguishing it from siblings like wafle_customers_get and wafle_customers_orders.

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 context is clear: it is a listing tool with pagination and filters. However, it does not explicitly mention alternatives or when not to use it (e.g., for single customer lookup), so it falls short of a 5.

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