retell_list_conversation_flow_components

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 operation is a list, which implies read-only, but does not disclose return format, pagination, or what fields are included. There is no mention of whether components are returned with configuration metadata or any statement about non-mutating behavior beyond the verb itself.

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 tight sentences: the first declares the action and scope, the second explains the concept. No unnecessary words, and the tool's purpose is front-loaded in the first 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?

The description fully covers the scope of the operation for a param-less list: it says 'all' and defines the resource. However, it does not describe the response shape or any filtering indicators, nor does it mention that a `get_conversation_flow_component` exists for single-item retrieval. For a simple list, this is adequate but could be slightly more complete.

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 has zero parameters, so schema description coverage is effectively 100%. Baseline for 0 params is 4; the description correctly omits parameter talk since there are none, and no additional meaning 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 ('shared Conversation Flow Components in your account'), clearly distinguishing it from sibling get/create/update/delete operations. It also defines what components are, which reinforces the resource identity and adds clarity beyond the tool name.

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 does not explicitly state when to use this tool versus alternatives like `retell_get_conversation_flow_component` for a single component. The purpose is implied by the list action, but no exclusions or alternative tool mentions are provided; a sentence mentioning the singular getter would improve guidance.

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