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 the export action and format, omitting potential side effects (e.g., API rate limits, session requirements, or behavior when the source is invalid). This is a significant gap for a data-export 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 concise sentence that front-loads the core action and scope. There is no extraneous information, and it is easy to parse at a glance.

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 five parameters, no output schema, and no annotations, the description is insufficient. It does not explain the dependency between source and listId (that listId is required when source is 'list'), nor does it describe the output structure or potential error conditions. An agent would need to infer these from the schema alone.

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 each parameter (source, listId, limit, fields, format). The tool description adds no additional meaning beyond what the schema provides, only repeating the format options. Baseline of 3 is appropriate when the schema does the heavy lifting.

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 specifies the action (export leads), the source (search results or a specific list), and the output format (JSON/CSV). It distinguishes itself from sibling tools like linkedin_search_leads (which finds leads) and linkedin_get_lead_profile (which retrieves a single profile), making its purpose unambiguous.

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 the two possible sources (current_search or list) but does not provide explicit guidance on when to choose this tool over alternatives, nor does it mention prerequisites such as having an active search session or a valid list ID. Usage context is only implied, with no exclusions or alternative references.

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