LinkedIn MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool adapts a CV and returns job details with an adapted CV, but lacks critical behavioral details: it doesn't specify if this is a read-only or mutation operation (though 'adapts' suggests generation, not modification), what permissions or authentication are needed, rate limits, or how the adaptation process works (e.g., AI-based, template-based). This leaves significant gaps for an agent to understand the tool's behavior.

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 appropriately sized and well-structured: it starts with a clear purpose statement, followed by separate 'Args' and 'Returns' sections. Each sentence adds value without redundancy. However, it could be slightly more front-loaded by integrating parameter roles into the initial statement for faster comprehension.

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 complexity (CV adaptation tool with 3 parameters), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It covers the basic purpose and parameters but misses behavioral context (e.g., how adaptation works, side effects), detailed parameter guidance, and output specifics beyond a string return. For a tool that likely involves data processing and generation, this leaves too many unknowns for effective agent use.

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 description includes an 'Args' section that lists the three parameters (position, location, job_id) and a 'Returns' section stating the output is a string with job details and adapted CV. However, schema description coverage is 0%, meaning the input schema provides no descriptions for parameters. The description adds basic semantics by naming the parameters and their roles, but doesn't elaborate on formats (e.g., what 'job_id' refers to), constraints, or examples, which is insufficient to fully compensate for the lack of schema documentation.

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 the tool's purpose: adapting a specific person's CV to a job description retrieved from LinkedIn based on position, location, and job ID. It specifies the verb ('Adapts'), resource ('Francisco Perez-Sorrosal's CV'), and target ('job description retrieved from linkedin'). However, it doesn't explicitly differentiate from sibling tools like get_jobs_raw_metadata or get_new_job_ids, which appear to be related to job data retrieval rather than CV adaptation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing job data from siblings), exclusions, or comparisons to other tools. The context implies it might follow job retrieval tools, but this is not stated explicitly, leaving usage unclear.

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