add_leads

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

With no annotations provided, the description carries the full burden and discloses key behaviors: bulk operation, deduplication of duplicate emails, the effect of skip_if_in_workspace, and the LOW_WRITE label. It does not explain what `confirm` does or what happens if both/neither target is specified, so it is not fully transparent.

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 core purpose is front-loaded in the first sentence, with supporting details compactly organized in a single paragraph using backticks for clarity. Every sentence adds value and there is no 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 write tool with no annotations and no output schema, the description covers purpose, target constraints, lead field semantics, deduplication behavior, and re-run safety. Missing details about `confirm` and target-conflict errors are notable but the description is still largely adequate for correct invocation.

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 0%, so the description compensates by detailing the `leads` array structure, required email for campaigns, optional fields, and custom_variables as a dict. It also implies the roles of campaign_id and list_id. However, `confirm` remains unexplained, preventing a perfect score.

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 the tool adds leads in bulk to a campaign or list, with a specific verb and resource. It also explicitly requires exactly one target, which distinguishes it from sibling lead management tools like update_lead or move_lead.

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 says when to use the tool: bulk adding leads to a campaign or list, with the 'provide exactly one target' constraint. It also notes that skip_if_in_workspace makes it safe for scheduled re-runs. It does not explicitly list alternatives for single-lead operations, but the usage context is clear.

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