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 meaningfully warns that private or out-of-network profiles will not be retrievable and may appear as 'LinkedIn Member', which is useful. However, it does not mention authentication requirements, potential error conditions, or response shape beyond the listed sections.

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 only four sentences and front-loads the core purpose immediately. The prerequisite, limitation, group, and billing information are each concise and useful, though the group and billing details are slightly tangential to the primary call semantics.

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 single-parameter read tool with no output schema, the description provides a solid return summary (full profile with experience, education, skills), a key limitation, and the source of the required parameter. It does not describe pagination or field details, but these are not essential for basic invocation.

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 for the memberId parameter, including its type, example, and a description matching the tool description. The description adds no new parameter meaning beyond repeating where to obtain the ID, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Returns a full profile including experience, education, and skills.' This clearly states what the tool does and distinguishes it from the sibling get_person_profile_posts by focusing on the profile content rather than posts.

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 gives a clear prerequisite by telling users how to obtain a memberId from /people/search or /company/{companyId}/employees. It also notes when profiles cannot be retrieved (private or outside network). However, it does not explicitly contrast this tool with alternatives like get_person_profile_posts, so usage guidance is implied rather than explicit.

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