addBulkCallContacts

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

Beyond the annotations, the description adds important behavior: repeated numbers are kept rather than merged, failed rows are reported in `rejected` while the rest are still added, and rows failing `call_conditions` get status `Skipped`. This is substantive operational context that an agent could not infer from the schema or annotations.

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 dense but focused: it front-loads the core purpose and then provides necessary caveats about duplicates, partial failures, and skipped rows. The tag 'Bulk calls' is mildly redundant, but no sentence feels wasted.

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 the nested schema and the absence of an output schema, the description covers the key operational details needed for correct use. It could go slightly further by describing the response shape beyond `rejected`, but the core invocation context is complete.

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 description coverage is 100%, so the parameters are already well documented. The description reinforces scale and batch behavior but does not meaningfully add parameter-level detail beyond what the schema provides, hence the baseline score of 3.

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 action and resource: 'Add up to 1000 contacts to a campaign in one request.' It also distinguishes this tool from the singluar form by calling itself the batch form, so an agent can tell it apart from siblings like addBulkCallContact without inspecting schemas.

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?

It explicitly says to prefer this tool 'whenever you have more than a handful' and explains the cost benefit. It also names the alternative ('Add contact to dynamic campaign'), giving the agent clear routing guidance between batch and single-add behavior.

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