create_audience_from_linkedin

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. However, it only says 'Import leads into an audience' without explaining key behaviors: whether existing leads are updated or duplicated, whether the import is synchronous, what authentication is needed, or what the outcome (success/failure) looks like. This is insufficient for a mutation tool.

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, front-loaded sentence that conveys the core action and resource without any wasted words. Every element—verb, resource, URL types—adds value.

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 the tool has 5 parameters (3 required), no output schema, and no annotations, the description is too brief. It does not explain what the tool returns (e.g., imported lead count, success message), how the LinkedIn post category parameter interacts with the URL, or any prerequisites (e.g., identity must be authenticated). The schema covers parameter formats but not operational context.

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%, and each parameter has a clear inline description (e.g., 'Identity ID to use for the LinkedIn import'). The tool description itself does not add extra meaning beyond the schema, but the schema already provides adequate semantics. Baseline 3 is appropriate.

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 'import' and clearly identifies the resource: 'leads into an audience from a LinkedIn URL'. It further specifies the types of LinkedIn URLs (regular search, Sales Navigator, or post URL), which immediately distinguishes it from sibling tools like list_members, search_lead, or remove_lead_from_audiences.

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 implies the use case (importing leads from LinkedIn) but provides no explicit guidance on when to use this tool vs alternatives like create_or_update_lead or search_lead. It does not state when not to use it or mention any prerequisites or context.

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