linkedin_analyse_job_fit

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds functional transparency by specifying the analysis outputs (match score, skills, keyword coverage, recommendations), giving the agent a clear picture of what the tool computes beyond the 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?

The description is two sentences with no waste. The first sentence front-loads the core function and outputs, and the second adds actionable usage guidance, earning every word's 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 tool with two parameters and no output schema, the description is self-contained: it explains the purpose, the decision context, and the return components (match score, skills, keyword coverage, recommendations). The agent has enough information to select and invoke the tool correctly.

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?

The input schema provides 100% coverage for both parameters ('job' accepts id/URN/URL, 'identifier' defaults to 'me'). The description adds no parameter-specific details, so the baseline of 3 is appropriate because the schema already does the heavy lifting.

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 uses a specific verb ('Compare') and resource ('user's profile against a job posting'), and enumerates concrete outputs (match score, required skills, keyword coverage, recommendations). This clearly distinguishes it from sibling tools like linkedin_analyse_profile and linkedin_apply_to_job.

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 second sentence explicitly states when to use the tool ('to decide whether a role is worth applying to') and what to emphasize if applying. It provides clear context but does not mention alternatives or when not to use, so it stops short of a full exclusion set.

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