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 OAuth authentication but fails to detail critical aspects such as required user interaction (e.g., redirects, consent screens), error handling, session management, or what happens upon success (e.g., token storage). This leaves significant gaps for an authentication tool.

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 concise and front-loaded, stating the core purpose in a single sentence. It avoids unnecessary details, but could be slightly more informative without sacrificing brevity. Every sentence earns its place, though it's minimal.

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 of an OAuth authentication tool with no annotations and no output schema, the description is incomplete. It does not explain the authentication flow, return values (e.g., tokens or status), error cases, or integration with other tools. This makes it inadequate for guiding an agent effectively.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details, which is appropriate, but it could have mentioned implicit parameters like OAuth scopes or credentials. Baseline is 4 due to the absence of parameters.

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 as 'Authenticate with LinkedIn OAuth' and specifies it 'works with standard LinkedIn Developer Application,' which provides context about the authentication method and compatibility. However, it does not explicitly differentiate from the sibling 'revoke_linkedin_auth,' which handles de-authentication, leaving some ambiguity in sibling distinction.

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 lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing LinkedIn credentials or setup), nor does it clarify its role relative to other tools like 'revoke_linkedin_auth' for managing authentication state. No when-not-to-use scenarios or alternatives are provided.

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