Import LinkedIn Leads from Target Companies

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

Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds valuable behavioral traits: variable cost per lead, dependency on external tools, and a note to confirm with the user before proceeding. No contradiction exists.

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 well-structured with a bold lead-in, bullet steps, and clear cost/category lines. It is front-loaded with the core purpose. Minor redundancy (title repeated in description) and length are acceptable given the complexity.

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?

The description covers core functionality, dependencies, and cost, but lacks details about the return format (e.g., what fields the leads contain, number of leads). Given no output schema, this omission makes the description slightly incomplete for an agent to handle results properly.

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 100%, so the description adds moderate value by explaining usage context (e.g., selecting a Google Sheet column, pasting a Sales Navigator URL). It also specifies that the company parameter expects a numeric ID only, going beyond the schema's generic description.

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 title and description clearly state that the tool imports LinkedIn leads from target companies. The steps describe crossing company URLs with Sales Navigator criteria, distinguishing it from sibling tools like derrick_search_companies or derrick_enrich_companies by specifying the exact use case (ABM, importing leads via Sales Navigator).

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 provides clear context: ideal for ABM, requires Derrick Chrome extension and Sales Navigator subscription, and notes variable cost requiring user confirmation. It does not explicitly state when not to use or compare to alternatives, but the context is sufficient for an agent to understand appropriate usage.

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