retell_publish_agent

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

With no annotations, the description carries the full burden. It discloses key side effects: creating an immutable version and starting a fresh draft, which are critical for understanding the tool's impact. However, it does not mention irreversibility, permission requirements, or other potential side effects like whether the previous version remains accessible.

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, well-structured sentence that is front-loaded with the primary action and includes the essential behavioral outcomes. No unnecessary words or repetition.

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 tool with one parameter and no output schema, the description sufficiently explains the tool's purpose and effects. It covers what the tool does and the resulting state changes, making it complete for its 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?

The input schema provides full coverage for agent_id with its own description. The tool description does not add additional meaning to the parameter, so the baseline 3 applies given 100% schema coverage.

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 tool's function: publish the latest draft of a voice agent, creating a new immutable version and starting a fresh draft. It uses a specific verb ('Publish'), identifies the resource ('voice agent'), and distinguishes it from similar tools like retell_publish_chat_agent by specifying voice agents.

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 by specifying it applies to voice agents, but it does not explicitly state when to use this tool versus alternatives or mention prerequisites. The presence of retell_publish_chat_agent in sibling tools hints at differentiation but without explicit guidance.

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