retell_create_conversation_flow_component

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only states the basic create action and the component's purpose; it does not mention any side effects, required permissions, idempotency, return value, or error conditions. This is a significant gap for a mutation tool.

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 extremely concise, consisting of two short sentences. It contains no redundant information or filler, immediately delivering the core purpose and context.

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 create operation with a well-documented schema, the description provides essential context about the tool's purpose. However, the absence of an output schema means the agent has no information about the return value, and the lack of behavioral notes (e.g., duplicate handling, permission requirements) leaves some gaps. It is adequate but not thorough.

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?

Schema description coverage is 100%, so the schema fully documents all four parameters. The description adds general context about the nature of components (reusable sub-flows) but does not provide additional specifics about parameter syntax or semantics beyond what the schema already offers.

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 action ('Create a new shared Conversation Flow Component') and defines what a component is ('reusable sub-flows that can be embedded across multiple Conversation Flows'). This distinguishes it from sibling tools like create_conversation_flow, which creates a full flow rather than a reusable component.

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 by explaining that components are reusable sub-flows embedded across multiple Conversation Flows, implying when to use this tool. However, it does not explicitly mention when not to use it or name alternative tools, but the context is sufficient for an agent to infer the appropriate scenario.

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