retell_get_chat

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

With no annotations provided, the description carries the burden of behavior disclosure. The verb 'Get' implies read-only, but it does not explicitly state 'read-only' or describe what the transcript contains (e.g., messages, timestamps). It also does not mention error behavior for invalid chat_ids. The description adds some context (details and transcript) but lacks depth.

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 verb 'Get,' and contains no unnecessary words. Every word earns its place.

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 tool with one parameter and no output schema, the description is nearly complete. It states what the tool returns (details and transcript) and the target (specific chat session). It could mention that the chat_id is required or that the tool only works for existing chats, but these are minor gaps given the simplicity.

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%, so the baseline is 3. The description only says 'specific chat session,' which aligns with the chat_id parameter's schema description ('The unique ID of the chat session.') without adding extra meaning or format details beyond the schema.

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 verb 'Get' and the resource 'details and transcript of a specific chat session.' It distinguishes from sibling tools like retell_list_chats (which lists all chats) and retell_get_chat_agent (which retrieves agent configuration), making its purpose unambiguous.

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: use this when you have a chat_id and want the details/transcript of that specific session. However, it does not explicitly provide when-to-use vs alternatives, such as 'to find a chat_id, use list_chats first.' No exclusions are mentioned, but the guidance is only implicit.

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