retell_publish_chat_agent

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

No annotations are provided, so the description carries the disclosure burden. It discloses that publishing creates a new immutable version, which is a key behavioral trait. However, it does not mention permissions, prerequisites (e.g., existence of a draft), or how this interacts with existing published versions beyond implying immutability.

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?

One sentence of 12 words, every word earns its place; front-loaded with the primary action and concise outcome. No redundancy or extraneous information.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the core action and result. Minor omissions: it doesn't state whether a draft must exist or what the response looks like, but these are not critical for invocation. Overall adequate for a simple publication operation.

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 single parameter agent_id is fully described in the schema (100% coverage), and the tool description does not add any additional semantic meaning to the parameter itself. Baseline of 3 applies because the schema already documents the parameter adequately.

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 ('Publish') and resource ('chat agent') with additional scoping ('latest draft') and outcome ('creating a new immutable version'), clearly distinguishing it from sibling tools like retell_publish_agent (for non-chat agents) and retell_get_chat_agent_versions (for listing).

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 makes it clear that this tool is for publishing chat agents, providing clear context for use. However, it does not explicitly contrast with alternatives such as retell_publish_agent or state when not to use this tool, so it lacks explicit exclusions.

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