retell_get_conversation_flow_component

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It simply says 'Get full details' without mentioning response format, error behavior, permissions, rate limits, or side effects. While 'Get' implies a read-only operation, the description does not add any meaningful behavioral context beyond what the name and schema already suggest.

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 sentence that front-loads the core action and resource. 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?

For a simple getter with one parameter and no output schema, the description is almost complete. It clearly states the purpose and implies usage, but it does not explicitly describe the return value or any error conditions. Nonetheless, the simplicity of the tool limits the need for more detail.

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 100% coverage, with the only parameter 'conversation_flow_component_id' described as 'The unique ID of the Conversation Flow Component to retrieve.' The description adds no additional parameter semantics, so the baseline of 3 applies.

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 retrieves full details of a specific shared Conversation Flow Component, using the specific verb 'Get' and resource. It distinguishes well from sibling tools like retell_get_conversation_flow (which gets a conversation flow, not a component) and retell_list_conversation_flow_components (which lists components).

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 implies when to use it: when you have a specific component ID and need its full details. It does not explicitly name alternatives or exclusions, but the context is clear given the tool name and the presence of a single required ID parameter. Since there is no explicit exclusion or alternative mention, it falls short of a 5.

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