Add Existing Lead to Campaign

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

Annotations only provide destructiveHint=false, so the description carries some responsibility. It adds the useful workflow precondition that the lead is already in the workspace, but it does not disclose behavior around duplicate membership, idempotency, or what happens if the campaign is inactive. No contradiction with 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 a single well-structured sentence with no wasted words. The parenthetical qualifier '(already in workspace)' adds meaningful context without bloat.

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 simple two-parameter operation with full schema coverage and an output schema, the description provides the key precondition (existing lead) and clear intent. It could be slightly more complete by naming when to prefer add_lead, but nothing critical is missing for 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 100%, so the parameter descriptions already document campaign_id and linkedin_url. The tool description adds context about the lead being existing but does not add new parameter-specific meaning beyond 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 uses a specific verb ('add') and resource ('existing lead ... to a campaign'), and clarifies the lead must already be in the workspace. This clearly differentiates it from sibling tools like add_lead or add_lead_to_list.

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 gives a clear usage condition: the lead must already exist in the workspace. However, it does not explicitly name alternatives or state when not to use this tool, such as for adding new leads.

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