sf_bulk_add_campaign_members

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

With no annotations, the description must disclose all behavioral traits. It fails to mention what happens if the 200 limit is exceeded, required permissions, error handling, or the return value. The status parameter's role and default behavior are also not explained.

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 single sentence is concise but lacks important details. It front-loads the action and capacity but omits parameter context. It could be improved by adding a second sentence clarifying required fields or default behaviors.

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 4 parameters, 1 required, no output schema, and no annotations, the description is insufficient. It does not explain the status field, constraints on leadIds/contactIds (e.g., at least one required for a meaningful operation), or what the function returns. The agent would need additional context to use this tool 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 0%, so the description must fully explain parameters. It only mentions 'leads and/or contacts' but does not describe the campaignId requirement, the meaning of the status parameter, or that leadIds/contactIds are optional arrays. This leaves critical ambiguity.

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 identifies the action ('Add'), the resource ('leads and/or contacts to a Salesforce campaign'), and the scope ('up to 200 in one call'). It distinguishes from the sibling 'sf_add_campaign_member' which likely adds a single member.

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 does not explicitly state when to use this tool over alternatives. While 'in one call' implies bulk use, there is no guidance on when to prefer this over the singular sibling or what constraints apply (e.g., at least one lead or contact required).

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