Import From Search

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

With no annotations, the description carries the full behavioral burden and only partially meets it: it discloses that results have "weaker intent" and require heavier post-filtering, useful context about output quality. It says nothing about permissions, rate limits, deduplication, or what happens on failure.

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?

Two short sentences, front-loaded with the core action, with no filler. "Weaker intent than a post import" is slightly terse/jargon-y but still earns its place as comparative guidance.

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?

An output schema exists, so return values need no explanation, but the description leaves two required parameters and a result cap undocumented and omits any behavioral detail for an annotation-less importing tool that creates lead records.

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 coverage is 0% for all three parameters, so the description must compensate but does not: list_id, search_url, and max_results (default 200) are never mentioned. The names are somewhat self-describing, but the default limit and the required identifiers are left entirely to 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?

States a specific verb (Import) and resource (leads) plus the source (LinkedIn or Sales Navigator search URL), which separates it from the URL-less import_leads and the post-based import_from_post. It does not explicitly name or contrast with import_leads, leaving some sibling ambiguity.

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?

"Use it when there is no relevant post" gives a clear when-to-use condition that routes the agent away from import_from_post. However, it never addresses when to prefer import_leads, and no exclusions or prerequisites are stated.

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