Customers_Listallcustomers

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

No annotations provided; description only says 'List all customers'. Does not disclose pagination, sorting, rate limits, or safety (read-only nature). Agent lacks key behavioral traits.

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?

Extremely concise, one sentence with no wasted words. Front-loaded with the core action.

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 simple list-all tool, description is adequate but lacks output format information (no output schema). Could mention pagination or result structure. Still, it conveys the basic functionality.

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?

Zero parameters; baseline set to 4 per instructions. Description adds no param info beyond schema, but schema coverage is 100% (no params to describe).

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 clearly states 'List all customers', identifying the verb (list) and resource (customers). It distinguishes from sibling 'Customers_Retrieveacustomer' which retrieves a single 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?

No guidance on when to use this tool versus other list tools (e.g., listCharges, Stores_Listallstores). Agent must infer usage from name alone.

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