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

With no annotations, the description carries the full behavioral burden, but it only says 'Searches' and 'uses filters.' It does not disclose any session/auth requirements, pagination behavior, output shape, LinkedIn scraping risks, or side-effect profile.

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 with no filler; the scoping clause comes first. However, for a 14-parameter tool it is quite sparse, so it is not optimized beyond brevity.

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 no annotations, no output schema, and 14 parameters, a one-sentence description is incomplete. It omits return format, pagination/startPage behavior, scraperMode meaning, session prerequisites, and how company inputs should be formatted.

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?

Only two of 14 parameters have schema descriptions (~14% coverage), so the description must compensate. It adds some meaning by saying the filter parameters mirror run_linkedin_people_search and it describes 'companies' and 'searchQuery,' but leaves most parameters (e.g., startPage, scraperMode, functionFilter) unexplained except by analogy.

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 precise operation: 'Searches LinkedIn employees of one or more given companies.' The reference to 'people-style filters as run_linkedin_people_search' also helps distinguish it from the company-focused sibling tools like run_linkedin_company_search. Required parameter 'companies' reinforces the resource.

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?

It makes clear the tool is for finding employees of specific companies, and points to run_linkedin_people_search for filter semantics. It does not explicitly state when not to use it or contrast it with other search tools, so it falls short of full exclusionary guidance.

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