linkedin_export_leads

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states what the tool does (export) without mentioning side effects, prerequisites, or whether it is read-only. The description does not clarify if an active search/session is required, what happens on invalid inputs, or if the export has any destructive impact.

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, front-loaded with the verb, and contains no redundant words. It efficiently communicates the essential action, source, and output format.

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 5-parameter schema with full description coverage, the description is mostly complete. It clearly identifies the two possible sources and output formats. Minor gaps include lack of behavioral nuance (e.g., active session requirement) but these are partially mitigated by the detailed schema.

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 baseline is 3. The description does not add additional meaning beyond the schema; it only mentions the two source options that are already captured by the 'source' parameter enum. No parameter syntax or format details are added beyond what the schema provides.

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 'Export' with a clear resource ('leads from LinkedIn Sales Navigator search results or a specific list') and output formats (JSON or CSV). It clearly distinguishes from sibling tools like searching, saving, or sending, which have different purposes.

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 states that the tool exports from 'current search results' or 'a specific list', giving clear usage context. It does not explicitly mention alternatives or when-not-to-use, but the context is sufficient for an agent to decide when to invoke it over sibling tools.

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