retell_list_chats

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

No annotations are provided, so the description carries the full burden. It implicitly indicates a read-only listing operation, but it does not disclose details such as pagination, response format, rate limits, or whether deleted chats are included. For a simple list tool, this is minimal but acceptable.

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, direct sentence with no filler. It is front-loaded and every word contributes to meaning. This is an appropriate size given the tool's simplicity.

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?

With no output schema and no annotations, the description should arguably explain more about what 'list' returns (e.g., an array of chat objects). It states the action clearly but does not describe the structure or any constraints. It is minimally complete for a zero-parameter list tool, but lacks depth.

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 tool has zero parameters and a fully covered empty schema. The baseline for 0 params is 4, and the description correctly does not invent any parameter semantics. Nothing more is needed.

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 ('List') and resource ('chat sessions') with clear scope ('in your Retell AI account'). It distinguishes this tool from sibling list tools by the resource type (chats vs. calls, phone numbers, voices, etc.), so the purpose is unambiguous.

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: use this when you need to list all chat sessions. It does not explicitly mention alternatives like retell_get_chat for a single chat, but it is evident from the sibling names and the simple listing action. There are no exclusions or special conditions stated.

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