setBulkCallNumberActive

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

It discloses key side effects beyond the annotations: dialing moves to the next number, the paused number keeps history and counters, the last active number cannot be paused, and setting the desired state makes retries harmless. These details explain both the operational impact and the idempotency behavior.

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 front-loaded with the core purpose and every paragraph earns its place: usage guidance, behavioral effects, a constraint, idempotency semantics, and a parameter disambiguation. It is detailed but not padded.

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 mutation tool with three required parameters, full schema coverage, and no output schema, the description provides enough context to invoke it correctly. It covers when to pause, when pausing is not allowed, the exact meaning of the ambiguous parameter, and the idempotent behavior.

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 the baseline is 3. The description adds crucial extra meaning for assignment_id, clarifying that it is the number's id within the campaign's pool and explicitly distinguishing it from phone_number_id. This is real semantic value 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?

The description opens with a specific verb and resource: 'Stop or resume dialing from one number in the pool.' It clearly identifies the tool's scope at the per-number level, distinguishing it from campaign-level siblings like setBulkCallConcurrency or bulkCallActions.

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 gives clear when-to-use guidance: 'Pausing is what you want when a number starts going bad mid-campaign.' It also states a meaningful exclusion: the last active number of a running campaign cannot be paused. However, it does not explicitly name alternative tools or say when to use one instead.

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