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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the chain context (owned job -> list applicants -> applicant.id), which is behavioral but not exhaustive (e.g., no mention of error conditions or return format). It adds value beyond annotations without contradicting them.

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 with no wasted words. The core purpose is front-loaded, and the prerequisite chain is stated compactly. Everything present earns its place.

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 simple read-only tool with annotations covering safety and a fully described schema, the description is nearly complete. It includes the essential chain that an agent must know to call it correctly. The only missing context is the exact return format, but that is not critical given the tool's simplicity and no output 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 all parameters are documented in the schema. The description itself does not add parameter-level meaning beyond the schema, which is appropriate given the high coverage. Baseline 3 is correct.

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 and resource: 'Get one applicant to a LinkedIn Classic job.' It also provides the prerequisite chain that distinguishes it from sibling tools like linkedin_classic_list_job_applicants (list) and linkedin_classic_get_applicant_resume (resume). The purpose is unambiguous and distinct.

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 'Required chain' explicitly tells the agent when to use this tool: after listing applicants and having applicant.id. It implies it should not be used before that step. While it doesn't explicitly mention alternatives, the chain is a clear usage guideline for sequencing.

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