wafle_exports_customers

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds behavioral detail by stating 'Wafle returns the raw CSV/JSON in the response body' and listing the exported fields. No contradiction exists, and the added response-body context is useful.

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 and well-structured: two short sentences front-load the core purpose and response format, followed by usage guidance and a caveat. Every sentence adds value with no redundancy.

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 sufficiently covers the export purpose, formats, included fields, and a performance caveat for large stores. However, given no output schema and low parameter coverage, it lacks detail on the segment and min_orders parameters and does not fully describe response edge cases, making it only partially complete.

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 low (25%, only slug is documented). The description mentions the default format (CSV) but does not explain the segment or min_orders parameters, leaving their semantics unclear. With limited schema coverage, the description should compensate, but it fails to do so for most parameters.

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 'Export the customer list of a store as CSV (default) or JSON' and lists the included fields (email, name, phone, total spent, order count, last seen). This specific verb+resource+format combination effectively distinguishes it from sibling export tools like wafle_exports_google_ads and wafle_exports_meta_audience.

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 provides explicit usage context: 'Use for CRM imports or general data exports.' It also advises an alternative for large stores ('prefer the dashboard download flow'), though it does not mention sibling tool names directly.

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