Get Company Employees

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

With annotations already declaring readOnlyHint and openWorldHint, the description adds meaningful behavioral context: it exposes demographics unique to this tool, notes page-count limitations relative to search_people, and requires the exact LinkedIn URL slug rather than display name. No contradictions with annotations.

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 front-loaded with the core purpose and remains efficient despite its length. Each sentence contributes essential information—unique demographics, sibling alternatives, page limits, exact slug requirement, and fallback guidance—without redundancy.

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 output schema exists and annotations cover safety, the description offers complete contextual guidance: what the tool returns, how it differs from search_people, how to obtain the correct input, and what the keywords parameter does. No critical gaps remain for an agent to effectively select and invoke the tool.

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?

Although schema coverage is 100%, the description significantly enriches parameter understanding. It explains that company_name must be the exact URL slug, provides a concrete counterexample (Anthropic's slug is 'anthropicresearch' not 'anthropic'), and clarifies the keywords filter scope, adding value beyond 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 states a specific action ('List employees at a company from the LinkedIn /people/ page') and clearly defines the resource and scope. It also distinguishes the tool from siblings by highlighting the unique demographics aggregate this view exposes.

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?

Explicit guidance is provided: when filtered search by network degree or location is needed, the description directs the agent to use search_people with current_company set, and notes that path returns more result pages. It also advises calling search_companies when the exact slug is uncertain.

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