linkedin_get_company_employees

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

The description does not disclose any behavioral traits such as what data is returned (e.g., names, profiles), pagination behavior, or authentication requirements. Since no annotations are present, the description carries full responsibility, and it falls short.

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, well-formed sentence that is front-loaded and contains no extraneous words. It effectively communicates the core functionality in a concise manner.

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 lack of output schema and annotations, the description is insufficiently complete. It does not explain what the output contains (e.g., fields returned), any limits on the number of employees listed, or how pagination works. Users would need additional information to use the tool effectively.

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 baseline is 3. The description adds minimal value by exemplifying 'job title' for the keyword filter, but it largely restates what the schema already explains. No additional semantic depth beyond the schema is provided.

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 lists employees at a company with an optional keyword filter. The verb 'list' and resource 'employees' are specific. However, it does not explicitly distinguish from sibling tools like 'linkedin_search_people' which might overlap in functionality, but the focus on company employees differentiates it.

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?

No guidelines are provided about when to use this tool versus alternatives. There is no mention of prerequisites, such as being logged in (linkedin_login), or when to use 'linkedin_search_people' instead for broader searches. The description lacks guidance on appropriate use cases.

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