customers_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says it lists customers, without explaining pagination behavior, date filtering semantics, the 'all' flag, dry_run behavior, or how WAROS balances are computed. The word 'Lista' implies a read operation, but adds little beyond the tool name.

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 sentence with no filler, and every word adds some information. It is concise and easy to parse, though the brevity leaves important operational details unstated.

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 tool with 7 parameters, no annotations, no output schema, and no schema-level parameter descriptions, a one-line purpose statement is insufficient. The description omits filter semantics, dry_run behavior, pagination, field selection, and how this tool relates to sibling customer/metrics tools.

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 7 parameters with 0% description coverage, and the description does not explain any of them. Terms like 'frecuencia', 'valor', 'ticket', and 'saldo WAROS' describe output fields, not parameter meaning. The agent receives no help understanding all, limit, offset, fields, date_from, date_to, or dry_run.

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 states a clear verb ('Lista') and resource ('clientes') and specifies the returned attributes: frequency, value, ticket, and WAROS balance. This makes the core purpose understandable, though it does not explicitly distinguish itself from sibling tools like customers_metrics or waros_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?

There is no guidance on when to use this tool versus alternatives such as customers_metrics, customers_detail, or waros_balances. No prerequisites, exclusions, or selection conditions are mentioned, leaving the agent to infer usage from the tool name alone.

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