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

Beyond the readOnly/openWorld annotations, it discloses that data is read live through the connected account and, critically, flags profile/post/company text as untrusted third-party data to be treated as data never instructions — a meaningful behavioral guardrail not present in the structured fields.

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?

Front-loads an 'Ids in / Ids out' hint and then a dense but purposeful sentence. Every clause carries information (returned fields, company enrichment, competitor-spotting, trust boundary), though the middle sentence is long and could be split for readability.

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?

With no output schema, the description fully enumerates the returned fields (profile card contents plus company industry/size/HQ/description) and covers the safety/trust dimension. An agent has everything needed to call it correctly and interpret the result.

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?

Schema coverage is 100%, so both profileUrl and connectionId are fully documented in the schema. The description's 'profile link or public identifier' and 'read through your connected account' restate what the schema already provides rather than adding syntax or edge-case detail. Baseline 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?

Names a specific verb and resource ('Get a rich profile card for ANY LinkedIn person by their profile URL') and enumerates exactly what is returned — name, headline, company/role, location, about, recent posts, plus company details. It clearly differentiates from siblings get_my_profile and get_profile_details by emphasizing 'ANY LinkedIn person' and the company enrichment.

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?

Gives explicit usage contexts: 'research a prospect before writing a personalized message' and 'use the company description to spot COMPETITORS ... and skip them.' That is clear when-to-use guidance. It does not, however, state when to prefer this over get_profile_details or get_my_profile, which are the closest siblings.

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