LinkedIn Intelligence MCP Server

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

No annotations are provided, so the description carries full burden. It mentions what the tool returns ('availability status and feature capabilities'), which is helpful. However, it doesn't disclose important behavioral traits like whether this is a read-only operation, potential rate limits, authentication requirements, or error conditions. For a tool with no annotation coverage, this leaves significant gaps.

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 extremely concise at just two sentences. The first sentence states the purpose, and the second describes the return value. Every word earns its place with zero waste or redundancy. It's appropriately front-loaded with the core functionality.

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 that the tool has no parameters, an output schema exists (which should document return values), and no annotations, the description provides basic but incomplete context. It states purpose and return types but lacks behavioral details needed for full understanding. The output schema should cover return values, so the description doesn't need to explain those, but other contextual gaps remain.

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 tool has zero parameters (schema coverage 100%), so no parameter documentation is needed. The description appropriately doesn't discuss parameters. With zero parameters, the baseline is 4, as there's nothing to compensate for and no redundancy with schema descriptions.

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: 'Check if browser automation is available for profile updates.' It specifies the action (check), target (browser automation), and context (for profile updates). However, it doesn't explicitly differentiate from sibling tools, as none appear to be direct alternatives for checking automation status.

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 implies usage context ('for profile updates'), suggesting this tool should be used when preparing to update profiles via automation. However, it doesn't provide explicit guidance on when to use this tool versus alternatives or when not to use it. No sibling tools appear to offer similar functionality, so differentiation isn't needed.

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