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

Annotations already carry readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the base safety profile is covered. The description adds non-redundant behavioral context: a hard prerequisite ('Resolve the exact Classic job_id first') and the constraint that filter values must be provider enums/IDs, which aligns with openWorldHint=false without contradicting it.

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 with no filler: purpose, prerequisite, and filter semantics each get exactly one sentence in priority order. The description is front-loaded with what the tool does, then gives only the call-critical caveats.

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 3-parameter tool with a nested filters object and no output schema, the description plus fully-covered schema supplies everything call-critical: scope, prerequisite, and filter semantics. The only gap is that return shape or pagination behavior is never hinted, which is a minor omission for a straightforward list tool.

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% — job_id, filters, and account_id each have substantive descriptions — so the baseline is 3. The description adds marginal semantic value by naming example filter dimensions ('ratings/experience') and re-emphasizing the enum/ID requirement, which helps an agent shape the nested filters object beyond the generic schema wording.

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 states a specific verb ('List'), a specific resource ('applicants for a LinkedIn Classic job owned by the connected account'), and the 'Classic' qualifier plus ownership scope distinguishes it from linkedin_recruiter_list_applicants and linkedin_classic_get_job_applicant. An agent can tell what this tool does and what it is not without opening the 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?

The description gives genuine usage context: 'Resolve the exact Classic job_id first' states a prerequisite, and the V2-filter guidance explains how to construct the call. However, it never explicitly names alternatives or states when-not-to-use (e.g., linkedin_recruiter_list_applicants for Recruiter projects), leaving sibling differentiation to the tool name and schema notes.

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