harvest_search_profiles

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only repeats filter capabilities and does not mention pagination behavior, result format, rate limits, or any other operational characteristics. This is a significant gap for a search tool with 14 optional parameters.

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, front-loaded sentence that clearly states the action and resource. There is no clutter or redundant information, making it easy to scan and understand quickly.

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 lacks critical context for a complex tool: no output schema, no pagination guidance, no indication of result limits, and no explanation of how multiple filters work together. Given the 14-parameter input and no annotations, the description is incomplete for an AI agent to invoke confidently.

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 all 14 parameters in detail. The tool description adds minimal value beyond listing a few filter types, but it does not clarify how parameters interact (e.g., geoId overrides location) or combine filters effectively. Baseline 3 is appropriate.

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's purpose: 'Search LinkedIn profiles' with specific filter dimensions (name, company, school, location, title, etc.). This verb+resource combination distinguishes it from sibling tools that search other entities like companies, jobs, or posts.

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: use this tool when you need to find LinkedIn profiles based on various criteria. It provides a clear context but does not explicitly mention alternatives or when not to use it, such as when to use harvest_search_leads or harvest_get_profile instead.

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