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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the exact result fields returned, the auto-resolution of text filter values to LinkedIn IDs, and the null-when-unreported semantics of total_count.

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, then returns, then filter resolution, then pagination. Each sentence carries information, though the filter-resolution sentence partially duplicates the schema descriptions. No filler or marketing language.

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 correctly takes on the burden of describing the returned fields and the pagination/nullability behavior, and it covers both invocation modes. The remaining gap is the missing boundary against closely related siblings such as linkedin_search_sales_navigator and linkedin_get_profile.

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 every parameter is already documented in the schema (including the url/keywords mutual exclusivity and the ID-resolution note). The description mostly restates that, adding only the cross-cutting point that text filter values are resolved automatically. Baseline 3 is appropriate when the schema carries the parameter burden.

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 and resource ('Search LinkedIn for people') and immediately names the two input modes (keywords/filters vs. a LinkedIn search URL). This separates it cleanly from linkedin_get_profile, linkedin_get_connections, and the other search siblings.

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 tells the agent both ways to drive the tool and points to cursor for follow-up pages, which is real usage guidance. It stops short of naming alternatives or exclusions, e.g. when to prefer linkedin_search_sales_navigator over this tool, so the agent must infer the boundary.

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