linkedin_export_search_results

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds the export formats (JSON, CSV, Markdown), which is a useful behavioral detail. However, it does not disclose session requirements, rate limits, pagination, or what 'any search' means in terms of verticals or scope.

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, direct and front-loaded, with no unnecessary words. It earns its place by conveying the core action and output formats efficiently.

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?

With 5 parameters and no output schema, this short description is insufficient. It does not explain what the output looks like (e.g., file, link, data object), how verticals and location work, or pagination behavior. The tool's complexity demands a more detailed description to be contextually complete.

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 only 40% (limit and format described). The description partially compensates by mentioning export formats, which clarifies the 'format' parameter, and 'Run any search' implies 'query' is the search term. But it does not address 'limit', 'location', or 'vertical', leaving significant gaps for required and optional parameters.

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 states the tool runs a search and exports results to JSON, CSV, or Markdown. This specific verb+resource combination distinguishes it from sibling tools like linkedin_export_companies or linkedin_search_people, which either export specific data types or search without explicit format options.

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 no explicit guidance on when to use this tool versus the many search and export siblings. It does not mention alternatives, exclusions, or scenarios where a specific search tool would be preferred. The phrase 'Run any search' implies broad usage but lacks concrete decision criteria.

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