startBulkCall

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is known. The description usefully adds the state-machine precondition (drafts only; running/scheduled/finished are rejected), but does not explain the real-world consequence of starting — outbound dialing, balance consumption, or reversibility.

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?

Three short paragraphs, front-loaded with the actionable sentence, then the draft lifecycle rationale, then the constraint. The '(Tags: Bulk calls)' footer is disposable, but overall there is little waste.

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 two-parameter mutation with no output schema, the description covers what to call it on and when it will be refused. The main remaining gap is what 'start' actually triggers (calls placed, spend incurred), which matters given destructiveHint=true.

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 100%, so bulk_call_id is documented in the schema; the description only alludes to the campaign it identifies. The empty requestBody property is neither explained nor clarified by the description, so nothing is added 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?

States a specific verb ('Start') and resource ('a campaign that was created with save_as_draft: true'), making the draft-only scope explicit. It implicitly separates this from createBulkCall/cancelBulkCall/retryBulkCall siblings, but never names or contrasts with them directly.

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?

Describes the intended workflow (create draft, add contacts in batches, set number pool and concurrency, then start) and gives a clear negative condition: a campaign already running, scheduled, or finished cannot be started. It stops short of pointing to alternative tools for those cases.

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