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

With no annotations, the description carries the full burden and does so well: it discloses pagination (25 per page), cache/fresh behavior, a flat 170-credit cost whether cached or not, and refunds on failed calls. It stops short of documenting auth requirements or rate limits, which is the only remaining gap.

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?

Purpose is front-loaded and the returned fields, cost, and usage are packed densely into one paragraph. Some phrasing ('The same object, and price, as linkedin/people...') leans redundant against the earlier sentence, but there is no filler.

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?

With no output schema, the description fully compensates by describing the returned object field-by-field plus pagination, pricing, refund policy, and cache semantics. Nothing an agent needs to call this correctly is missing.

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 parameters are already fully documented. The description only restates company_id provenance ('company_id in linkedin/company') and implies cursor-based paging, adding little beyond the schema, which justifies the baseline 3.

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 specific verb+resource ('Fetch the people who list a company as their employer') and enumerates the exact return shape (name, location, profile, roles with title, employer, company_id, start month). It also anchors itself to a sibling ('the same object as linkedin/people with source=sales_navigator'), so an agent can distinguish it from other LinkedIn endpoints without opening a schema.

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?

Gives clear usage intent ('Use this to map a company's team or to find who to contact') and cross-references the equivalent linkedin/people call. It does not, however, spell out when-not-to-use it or contrast it against in-domain siblings like search_linkedin_people, leaving the routing choice partly inferential.

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