gerent365_list_customers

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

No annotations are present, so the description must carry the full burden. It states a simple list operation, implying a safe read, but does not disclose pagination, ordering, or return format. For a zero-parameter list, this is minimally adequate but lacks behavioral details beyond the obvious.

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, concise Spanish sentence that directly conveys the action. It is appropriately sized and front-loaded with the key information, with 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?

Given the low complexity (no params, no output schema), the description is adequate but misses the opportunity to differentiate from gerent365_search_customers or mention ordering/pagination. Since there is no output schema, the agent receives no guidance on the shape of returned data, so completeness is moderate.

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?

There are zero parameters, and the schema is empty, so baseline 4 is appropriate. The description adds no parameter information because none exist.

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 uses a specific verb ('Lista' = lists) and resource ('clientes' = customers), clearly indicating a read operation that returns business customers. It distinguishes from siblings like search_customers (which implies filtering) and create/update customers. Although it doesn't explicitly say 'all', it is clear enough.

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 no guidance on when to use this tool versus alternatives like gerent365_search_customers. It does not mention filtering capabilities or imply any specific use case beyond listing all customers, so no context or exclusions are provided.

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