LinkedIn Intelligence 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. It mentions the browser automation requirement and implies a write operation ('Add'), but lacks details on permissions, side effects, or error handling. It adds some context but not comprehensive behavioral traits.

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 front-loaded with the core purpose, followed by prerequisite and parameter details in a structured format. Every sentence adds value with zero waste, making it highly efficient and easy to parse.

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 moderate complexity (a write operation with one parameter) and the presence of an output schema (handling return values), the description is fairly complete. It covers purpose, prerequisite, parameter, and return, though could improve on behavioral details like error cases.

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 explicitly documents the single parameter ('skill_name: Name of the skill to add'), adding meaning beyond the 0% schema coverage. Since there's only one parameter and it's fully explained, this compensates well for the schema gap, though not perfectly (e.g., format constraints).

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 action ('Add a skill') and target ('to your profile'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'get_profile_skills' or 'update_profile_headline', which would require a 5.

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 includes a prerequisite ('Requires Playwright browser automation to be enabled'), which provides some usage context. However, it doesn't specify when to use this tool versus alternatives (e.g., 'update_profile_summary') or any exclusions, keeping it at an implied level.

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