dispatch_voice_campaign

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

With no annotations provided, the description carries full burden and discloses key behaviors: voicemail drop on no-answer, live transfer on trigger, TCPA compliance (DNC scrub, timezone window), and outcome flow via webhook. It does not mention rate limits or failure modes, but covers critical operational details.

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?

Four sentences, front-loaded with main purpose. Includes necessary technical details but could be slightly more streamlined. No repetition of schema info.

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 10 parameters and no output schema/annotations, the description explains core workflow and compliance but lacks details on error handling, outcome event structure, or post-call operations. Sufficient for basic understanding but not exhaustive.

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 coverage is 90% (high), so baseline is 3. The description adds value beyond the schema by explaining how parameters like system_prompt and greeting are used in the conversation, and that voice_id defaults to 'rachel'. It ties parameters to real-world effects.

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 'Place outbound phone calls to the granted audience' and distinguishes from sibling email/SMS campaign tools by specifying the telephony stack (Vapi, ElevenLabs, Claude). It is specific and directly reflects the tool's function.

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 explicit guidance on when to use this tool vs alternatives like dispatch_email_campaign or dispatch_sms_campaign. The description focuses on how it works (e.g., voicemail drop, live transfer) but omits usage context such as 'use for voice outreach only' or 'requires granted audience'.

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