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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral context: the job_id must be resolved first, and filters are strictly constrained to documented enums/IDs. It does not cover pagination or return format, but given the annotations and the schema's richness, this is acceptable. No contradiction with annotations.

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?

Two sentences, front-loaded with the core action and scope, then a necessary prerequisite and a caution about filters. No wasted words, every sentence earns its place. Ideal structure for quick agent parsing.

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?

Given the tool's complexity (list operation with optional filters, no output schema), the description covers the essential points: what it does, the critical job_id prerequisite, and filter constraints. It doesn't mention pagination or return format, but that is common for list tools and the annotations/schema cover the safety and parameter details. It could explicitly contrast with the Recruiter sibling, but the naming and description already convey the Classic scope. Overall, it is sufficiently complete for correct invocation.

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 each parameter already has detailed semantics. The description adds a high-level instruction ('Resolve the exact Classic job_id first') which is more of a usage guideline than parameter semantics. The filter guidance about enums is somewhat redundant with the schema's 'Use documented enum/filter IDs; omit unknown filters rather than guessing.' The description does not materially enhance parameter understanding beyond the schema, so baseline 3 is appropriate.

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 clearly states 'List applicants for a LinkedIn Classic job owned by the connected account.' It names the specific verb (list), resource (applicants for a Classic job), and ownership scope (connected account). It also distinguishes from siblings like linkedin_recruiter_list_applicants by explicitly mentioning 'Classic' and 'owned by the connected account', so an agent can tell it apart without opening schemas.

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 a crucial prerequisite: 'Resolve the exact Classic job_id first.' It also instructs that filters must use provider enums/IDs rather than guessed display values. It does not explicitly name alternatives like the Recruiter list tool, but the 'Classic' qualifier and naming make the intended context clear. Slight improvement would be to explicitly say 'Use this for Classic jobs; use linkedin_recruiter_list_applicants for Recruiter projects.'

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