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

Goes well beyond the readOnly/idempotent annotations by stating "The person is not notified" — the key behavioral fact for a profile view. It also discloses per-plan rate limits (100/day free, 150 Sales Navigator, 200 Recruiter, fewer in early weeks) and that each lookup consumes one profile view, none of which the annotations convey.

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-loaded with what the tool returns before moving to identifier forms, plan behavior, and quotas. It is dense but nearly every clause adds information; the trailing "fewer in the first weeks after connecting" is the one vague, low-value fragment.

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?

There is no output schema, so describing the returned fields and the extra linkedin block (connection degree, shared connections, InMail eligibility, open profile) is essential and done well. The unexplained required account_id and the unspecified shape of the linkedin block keep it short of 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?

With 0% schema description coverage, the description carries the load and mostly succeeds: it explains identifier formats, the api plan values and the member-id requirement, and enumerates the sections values including a useful note that skills carry the endorsement_id used by endorse_skill. The required account_id parameter is never explained, leaving one gap.

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?

"A person's profile on a connected account" gives a clear verb-like resource and enumerates the returned fields (name, headline, location, profile URL, connection degree). It clearly reads as someone else's profile, which implicitly separates it from get_own_profile, but it never names that sibling to make the distinction explicit.

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?

Explains the conditions that shape a call: which identifier forms are valid on LinkedIn, and that Sales Navigator or Recruiter plans require the member id via the api parameter. It gives quotas per plan, which effectively tells the agent when a call is affordable, but offers no explicit exclusions or named alternatives.

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