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

Annotations declare readOnlyHint and openWorldHint, so the description only needs to add extra behavior. It adds that the tool returns a list and mentions pagination with cursor, which is useful and goes beyond the annotations. There is no contradiction.

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?

A single, purposeful sentence that front-loads the core action and follows with a brief note on pagination. No filler or redundant wording.

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?

For a read-only tool with one parameter and no output schema, the description adequately covers purpose, input format, and pagination behavior. It omits details like return structure, but given the simplicity and available schema/annotations, it is nearly complete.

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 already provides 100% coverage, describing the 'url' parameter as accepting LinkedIn profile URL, vanity handle, '@handle', or 'in/{handle}' path. The description adds no further parameter details beyond echoing 'by URL or handle', so the baseline of 3 applies.

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 it gets LinkedIn person profiles via URL or handle, distinguishing it from sibling tools like linkedin_company_get or linkedin_people_search_list. It names the specific resource type (person profiles) and the method of lookup, leaving no ambiguity about which tool to use for direct profile retrieval.

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?

It conveys that this tool is for direct lookup by URL/handle, implying it should be used when the exact identifier is known, as opposed to search tools. However, it does not explicitly name alternatives or state when not to use it, so it falls just short of a 5.

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