Add Lead to List & Campaign

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

The description only says 'Add a lead' and does not disclose behavior beyond what the non-destructive annotations and schema already convey. It does not mention idempotency, duplicate handling, whether the lead must already exist, or what side effects may occur.

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 a single sentence with no filler or redundant elaboration. It is front-loaded with the action and resource, but it is also minimal to the point of omitting helpful contextual distinctions.

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 that the schema and output schema cover parameter semantics and return shape, the description is adequate for basic invocation. However, the existence of sibling tools performing narrower versions of the same action means an agent lacks enough context to reliably select between add_lead, add_lead_to_list, and add_existing_lead_to_campaign.

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 schema already documents linkedin_url, list_id, campaign_id, and the optional data mapping. The description adds no parameter-level meaning beyond saying 'by LinkedIn URL,' which is already reflected in the schema.

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: it adds a lead to a Prosp contact list and campaign, identified by LinkedIn URL. This clearly conveys the combined action and is more specific than the title alone, though it does not explicitly distinguish itself from the sibling tools add_lead_to_list and add_existing_lead_to_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?

No guidance is provided about when to use this combined tool versus the separate add_lead_to_list or add_existing_lead_to_campaign tools. The description names the operation but gives no exclusions, preconditions, or alternative routing.

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