harvest_search_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 that the tool 'supports 30+ filter params' without mentioning pagination, result limits, authentication requirements, or return format. This leaves the agent without critical context for invoking the tool correctly.

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 compact, with two sentences that directly state the purpose and scope. The second sentence about '30+ filter params' is a bit redundant with 'advanced inclusion/exclusion filters' but still adds a quantitative detail. No unnecessary filler.

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's complexity (36 parameters, no output schema), the description is too sparse. It provides no high-level guidance on constructing searches, typical use cases, or return values. The schema handles parameter details, but the description fails to give the agent a broader behavioral and usage 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?

The input schema has 100% coverage of all 36 parameters with detailed descriptions, so the baseline is 3. The description adds no specific parameter semantics beyond a vague count of filters; it does not clarify relationships like salesNavUrl overriding other parameters (which is already in 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 ('Search') and resource ('LinkedIn leads (Sales Navigator)'), clearly distinguishing it from sibling tools like harvest_search_profiles or harvest_search_companies. It also mentions the key feature of advanced inclusion/exclusion filters, which helps the agent understand the tool's scope.

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 usage for searching LinkedIn leads, but it does not explicitly state when to use it over alternatives or mention exclusions. Sibling tool names differentiate by resource type, but no explicit guidance is given about selecting this tool versus others or about handling Sales Navigator URLs versus individual filters.

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