retell_create_chat

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

The description discloses no behavioral details such as side effects, return values, permissions, or whether the session is persistent. With no annotations provided to compensate, the agent has no information about what happens after starting 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 concise sentence with no redundant wording. It is appropriately front-loaded and avoids unnecessary detail.

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 description is minimal and does not explain the return value or session lifecycle. Given that the tool creates a chat session, an agent would need to know what the session object looks like, any prerequisites, or how to reference it later. The schema covers parameters but not the tool's overall 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?

All four parameters are described in the input schema with 100% coverage, so the baseline is 3. The description does not add additional meaning to the parameters; the schema is sufficient for understanding them.

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 ('Start') and resource ('chat session'), clearly stating the tool's action. It is distinct from sibling tools like retell_create_chat_completion and retell_create_sms_chat, which involve different operations on chat or sessions.

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?

No guidance is provided on when to use this tool versus alternatives such as create_chat_completion, create_sms_chat, or create_web_call. The description only states the action, leaving the agent without context for tool selection.

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