sf_add_campaign_member

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

Annotations only show destructiveHint: false. Description discloses it creates a non-destructive record, returns the created membership, and mentions status defaults. No hidden side effects; adds useful behavioral context beyond 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?

Two paragraphs: first with instructions, second a summary. Front-loaded with purpose. Some redundancy (e.g., 'Add a lead or contact...' echoes first sentence), but generally efficient.

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?

No output schema, but description mentions return value. Covers key aspects: what it does, parameter constraints, status options. Lacks error handling or prerequisite info (e.g., campaign must exist), but adequate for a simple create tool.

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% (baseline 3). Description adds mutual exclusivity of contactId/leadId, default status, and possible status values, enhancing understanding beyond the schema alone.

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 states it creates a CampaignMember junction record linking a Lead or Contact to a Campaign, distinguishing it from sibling tools like sf_campaign_members (list) and sf_create_campaign (create campaign).

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?

Provides explicit instructions: provide campaignId and either contactId OR leadId, and explains status defaults and options. Lacks explicit when-not-to-use or alternatives, but the context is clear.

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