retell_list_conversation_flows

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 states the read-only nature implicitly via 'List' and explains what Conversation Flows are, but it does not disclose pagination, result size, or that full details may be obtained via get_conversation_flow. It is honest but minimal.

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, both earning their place. The first states the action and scope; the second defines the entity type. No fluff, front-loaded, and easily scannable.

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 parameterless list tool, the description is complete. It names the resource, scope, and provides a definition of Conversation Flows. No output schema exists, but the return value (a list of flows) is implied sufficiently.

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 0 parameters, and the schema is empty (100% coverage). Per the baseline for 0 parameters, a score of 4 is appropriate. The description does not need to add parameter details since 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 clearly states the tool lists all Conversation Flows in the Retell AI account, using a specific verb and resource. It differentiates from sibling tools like get_conversation_flow or create_conversation_flow by emphasizing 'all' flows.

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 clear context for when to use the tool (to list all flows), but it does not explicitly mention alternatives for listing vs. retrieving a single flow. The 'all' scope and sibling tool names make the usage obvious, but explicit exclusions are absent.

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