retell_create_chat_completion

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

No annotations are provided, so the description must disclose behavioral traits on its own. It only states the immediate action and response, but does not mention that sending a message mutates the chat state, potential side effects, permissions, error behavior, or response format. This is a significant gap for a tool that modifies a session.

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, efficient sentence that front-loads the action verb and clearly states the expected outcome. There is no filler or redundancy; every word contributes to the meaning.

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?

The tool has a simple signature, but there is no output schema and no annotations. The description does not cover prerequisites (e.g., how to obtain chat_id), the exact structure of the response, or side effects. The information provided is insufficient for an agent to fully understand the tool's behavior and 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%, with both parameters already described ('chat_id' and 'content'). The description adds no additional meaning or detail beyond what the schema already 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 uses a specific verb ('send') and names the resource ('user message to an ongoing chat session'), clearly indicating the action and what is returned ('get the agent's response'). This distinguishes it from sibling tools like retell_create_chat (which creates a session) or retell_update_chat (which updates settings).

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 phrase 'ongoing chat session' implies the tool requires an existing chat_id, providing some usage context, but it does not explicitly state when to use this tool versus alternatives or mention exclusions. The guidance is implied rather than clearly articulated.

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