retell_delete_chat_agent

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does state the operation is permanent, which is a crucial destructive trait. However, it does not mention permissions, side effects, or error behavior, which are relevant 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 a single sentence, front-loaded with the action and object. It contains no unnecessary words or redundancy, making it highly concise and well-structured.

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 single-parameter delete operation, the description is complete enough: it identifies the resource, specifies permanent deletion, and the parameter is well-documented. The absence of an output schema makes return value details less critical, though a note on result or error could elevate completeness.

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 single parameter, agent_id, fully described in the schema as 'The unique ID of the chat agent to delete.' The description adds no extra parameter semantics beyond confirming the ID's role.

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 ('Permanently delete') and resource ('chat agent') with a clear method ('by its ID'). This distinguishes it from sibling delete tools like retell_delete_agent and retell_delete_phone_number, making the purpose unmistakable.

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 based on the resource type 'chat agent' but does not explicitly state when to use this tool versus alternatives like retell_delete_agent. No exclusions or alternative pointers are provided, leaving the guidelines somewhat implicit.

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