LinkedIn Custom MCP Server

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

The description adds value beyond annotations by specifying the data fields returned (Name, Email, Picture), which isn't covered in annotations. However, it doesn't disclose additional behavioral traits like authentication requirements, rate limits, or error handling. With annotations limited to title only, the description carries more burden but does not fully compensate.

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 a single, well-structured sentence that efficiently conveys the tool's purpose, scope, and output fields. It is front-loaded with the key action and resource, with no wasted words.

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 low complexity (0 parameters, read-only operation implied by 'Fetch'), an output schema exists, and annotations are minimal, the description is reasonably complete. It specifies the returned data fields, which complements the output schema. However, it could benefit from mentioning authentication context or usage constraints.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose without redundant parameter info, earning a high score for efficiency.

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 specific action ('Fetch') and resource ('authenticated user's profile information'), explicitly listing the data fields returned (Name, Email, Picture). It distinguishes from siblings like 'linkedin_get_member_profile' by specifying it's for the authenticated user only.

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 explicitly states when to use this tool: to fetch the authenticated user's profile. It implies when not to use it (e.g., for other users' profiles, where 'linkedin_get_member_profile' would be the alternative). This provides clear context for selection among sibling tools.

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