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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuine behavioral context beyond them: the subscription prerequisite, that text filters are auto-resolved to LinkedIn IDs, and that results carry fields (open profile status, premium status, tenure) that classic search does not return.

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?

Four sentences, front-loaded with purpose before the caveats, and each sentence carries real information (search modes, richer output, subscription requirement, ID resolution). The trailing 'and more' is the only mildly wasteful phrase.

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?

For a 10-parameter, all-optional search tool with no output schema, the description covers the prerequisite, both input modes, and the shape of the returned data well enough to call it correctly. It could say slightly more about pagination behavior or result limits, but the cursor semantics are already in the schema.

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 every parameter, including the 'resolved to LinkedIn IDs automatically' note for function/industry/location. The description's ID-resolution sentence restates that rather than extending it, so this sits at the baseline for a fully documented 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 names a specific verb and resource ('Search LinkedIn Sales Navigator for people') and explicitly contrasts the result set with 'classic search,' which routes the agent away from the sibling linkedin_search_people. It also states the two distinct input modes (keywords/filters vs. a pasted search URL), so the tool's identity is unambiguous.

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 gives a real usage gate ('Requires a Sales Navigator subscription on the connected LinkedIn account') and notes the mutual exclusivity of url versus keywords/filters. What is missing is an explicit 'prefer this over linkedin_search_people when X' rule; the richer-results comparison implies it but leaves the selection slightly to inference.

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