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

Annotations already cover readOnly/idempotent/openWorld, so the bar is lower, and the description adds two things not found in structured data: the result ordering ('newest first') and that the call is metered as browsing activity. It stops short of describing pagination behavior or any depth/detail limits.

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?

Three short fragments, front-loaded with the platform restriction and the resource definition. Nothing is redundant, though the terseness contributes to the gaps elsewhere rather than being tight discipline over rich content.

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 cursor-paginated list tool with no output schema and zero schema-level parameter descriptions, the definition leaves the agent guessing about page shape, default page size, and pagination flow. The ordering note is helpful, but an agent cannot complete a multi-page traversal from this text alone.

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 description coverage is 0% for three parameters, so the description must carry the load and it does not. It never explains what 'limit' bounds (max 100), how 'cursor' is obtained from a prior response, or why 'account_id' is required beyond a vague possessive 'This account's'.

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?

States a specific resource and scope: 'This account's 1st-degree connections, newest first.' The '1st-degree connections' phrasing does distinguish it in kind from followers/following/invitation tools, though the description never names those alternatives to confirm the boundary.

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?

'LinkedIn accounts only' establishes a platform precondition, and 'Counts as browsing' signals a quota/cost implication for the caller. But there is no explicit when-to-use versus when-not guidance relative to the many sibling list_* tools (e.g. followers vs. following vs. invitations).

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