retell_list_agents

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

With no annotations, the description must fully disclose behavior. It states the return fields (IDs, names, voice settings, configuration), which is helpful, but it does not mention whether results are paginated, any rate limits, or explicitly confirm this is a read-only operation (though 'list' implies it). No contradictions.

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?

Two sentences, no filler. Every word adds value, and the key purpose is front-loaded with the return information in the second sentence.

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 tool with no parameters and no output schema, the description provides a clear statement of action and return values. It is sufficient for an agent to understand the tool's scope and output, despite the large sibling set.

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 is empty (0 parameters), so the baseline is 4. The description adds no parameter details, but there are none to describe, so it meets the baseline without needing further elaboration.

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 the specific verb 'List' with the resource 'all Retell AI voice agents in your account', clearly distinguishing it from sibling tools like retell_list_phone_numbers and retell_list_voices. It also enumerates the return data (agent IDs, names, voice settings, configuration), making the purpose 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 description provides no guidance on when to use this tool versus alternatives such as retell_get_agent for individual agents or retell_list_phone_numbers for phone numbers. There are no exclusions or contextual cues beyond the name and generic list semantics, so the agent gets no explicit direction.

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