retell_delete_conversation_flow_component

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it reveals a significant side effect: 'local copies are automatically created in all Conversation Flows that use it.' This goes beyond a simple delete statement and helps the agent understand the impact. It does not mention permissions or reversibility, but the disclosed side effect is a critical behavioral trait.

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 two concise sentences, with the action front-loaded in the first sentence and the key consequence in the second. There is no redundant or filler content, making it highly efficient for an agent to parse.

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 deletion tool with one parameter and no output schema, the description covers the primary action and the most important consequence (local copy creation). It does not explain return value or error handling, but those are less critical given the tool's low complexity and the presence of related sibling tools that add context.

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%, as the parameter 'conversation_flow_component_id' already has a description in the schema. The tool description does not add additional semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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 ('Delete') and the specific resource ('shared Conversation Flow Component'), which distinguishes it from sibling delete tools like 'retell_delete_conversation_flow' and 'retell_delete_agent'. The second sentence adds a key behavior that further defines the purpose by explaining what happens when the component is deleted.

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 context that this tool is for deleting shared components, but it does not explicitly advise when to use it versus alternatives or mention any exclusions. The sibling list includes related operations (create/update/list components), so the usage intent is implied but not directly stated.

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