setBulkCallConcurrency

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

Annotations already indicate this is a non-read-only, non-destructive mutation. The description adds behavioral context beyond that: the change can be applied to a running campaign, and the effective ceiling is the account's concurrency limit. This helps an agent understand the impact without over-promising specifics.

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 short, front-loaded with the primary action, and every sentence contributes: purpose, runtime applicability, operational tradeoffs, and the account limit constraint. There is no redundant filler.

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 simple two-parameter setter, the description covers the core behavior, valid timing, value-selection guidance, and the limiting constraint. It does not describe the response shape, but no output schema exists and a straightforward mutation like this can reasonably omit that detail. Overall it gives an agent enough to call it correctly.

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 descriptions already define bulk_call_id and concurrent_call_limit. The description adds decision-making semantics for concurrent_call_limit — 'Raise it to finish sooner, lower it if your team cannot keep up' — which helps an agent choose an appropriate value rather than merely passing the field.

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 states a specific verb and resource: 'Change how many calls the campaign places at once' — clearly identifying the bulk-call concurrency setting. This distinguishes it from sibling tools like setBulkCallDailyTimeControl or setBulkCallNumberActive by focusing on the concurrency dimension.

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 situational guidance: raise concurrency to finish sooner, lower it if the team cannot keep up or numbers are answered less. It also notes the operation is valid 'while it is running.' It does not explicitly name alternatives or exclusion conditions, but the context is clear enough for an agent to decide when this tool fits.

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