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

Annotations already cover readOnly/idempotent/openWorld/non-destructive, and the description adds value beyond them by disclosing the Recruiter-capable-account authorization requirement and the inability to persist searches or custom filters. It does not describe result shape or pagination, which is the main 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?

Three sentences, front-loaded with the core action and account constraint, then usage scope, then the helper and the capability limitation. 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?

For a read tool with annotations plus a partially documented schema and no output schema, the description is nearly sufficient: it covers purpose, scope, account requirement, and the unsupported single-shot save behavior. It could add a note on result return/pagination, but nothing critical for correct invocation 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 low (33%), and the two save_* properties carry an opaque 'not: {}' schema that actively conveys nothing. The description compensates by explaining that saving searches/custom filters is unsupported and by pointing at linkedin_get_search_parameters for filter IDs, while account_id is already well documented in 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?

States a specific verb+resource ('Search LinkedIn Recruiter candidates') and qualifies the required account type ('Recruiter-capable account'), which cleanly separates it from the general-persona siblings like linkedin_search_people, linkedin_sales_navigator_search_people, and linkedin_search_from_url.

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 concrete when-to-use contexts (candidate sourcing, recruiting projects/talent pools, Recruiter-specific filters) and a when-not capability constraint ('cannot save searches or custom filters'), plus the prerequisite tool for filter IDs. It stops short of explicitly naming the non-Recruiter alternatives to use instead, so it is clear but not fully routing.

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