retell_delete_conversation_flow

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

With no annotations provided, the description carries the full burden. It clearly discloses irreversible deletion ('permanently') and the cascading effect on versions ('all its versions'), which is critical behavioral context. It does not mention auth or error behavior, but the key destructive traits are covered.

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?

A single, concise sentence that front-loads the action and effect. Every word is useful; no wasted text or repetition of schema details.

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 one-parameter delete tool, the description provides essential context: the operation is permanent and affects all versions. While it lacks details on return values or error states, the simplicity of the operation makes this sufficient. No output schema exists, but the description adequately explains the tool's primary effect.

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 coverage is 100% with a clear parameter description ('The unique ID of the Conversation Flow to delete'). The tool description adds context about deleting versions, but adds no extra meaning specifically about the parameter itself. Baseline 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'), the resource ('Conversation Flow'), and the scope ('all its versions'). This distinguishes it from sibling delete tools like 'delete_conversation_flow_component' by explicitly focusing on the flow itself.

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 usage for deleting a Conversation Flow, but it does not explicitly mention when to use this tool over alternatives (e.g., delete_conversation_flow_component) or any prerequisites. The scope is understandable from context but lacks explicit when/when-not guidance.

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