retell_update_chat

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only states the mutation action without explaining permissions, merge/replace semantics, effects of changing data_storage_setting, or response format. This is similar to the under-specified update_drive example.

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 that is front-loaded with the action ('Update') and contains no filler or redundant words. It is appropriately brief 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?

With four parameters including a nested object, no output schema, and no annotations, this description is too sparse. It omits a major capability (override_dynamic_variables), provides no usage context or alternatives, and does not address behavioral details, leaving the agent under-informed for correct invocation.

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?

The input schema already describes all four parameters with 100% coverage, so the baseline is 3. The description redundantly mentions metadata and data_storage_setting but adds no extra meaning beyond the schema, and it does not mention override_dynamic_variables.

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 the specific verb 'Update' with the resource 'ongoing chat session' and mentions specific fields (metadata, data storage settings). It distinguishes from sibling tools like retell_update_chat_agent, but omits the override_dynamic_variables capability, making the scope incomplete.

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?

There is no guidance on when to use this tool versus alternatives such as retell_update_chat_agent or retell_update_call. The phrase 'ongoing chat session' only implies a context but does not provide explicit when/when-not decision criteria or mention alternative tools.

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