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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely new operational context: a hard pacing limit of 3 calls/minute per account and cursor-based pagination. It doesn't say what an empty result implies (no shared connections vs. an inaccessible profile), which would be the last piece.

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?

Four short sentences, all front-loaded: purpose first, then the accepted identifier forms, then pagination, then pacing. Nothing is redundant with itself and every sentence carries usable information.

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 read-only annotations, a fully documented 2-parameter schema and no output schema, the description covers what to pass, how to page, and how fast you may call it. An agent is still left guessing at the shape of each returned connection, a minor gap given there is no output schema.

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% and both parameters are fully described in the schema, including the URL/slug/URN forms that the description repeats. The description adds no format or resolution details beyond the schema, 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?

States a precise verb and resource — mutual/shared connections between the caller and a target profile — and defines the concept inline ('the people in your 1st-degree network who are also connected to the target'). This clearly separates it from linkedin_get_connections (own network) and linkedin_search_people.

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 concrete intent ('finding who can give a warm introduction') and an explicit batch constraint ('Look up one person at a time'), plus a rate limit of 3 lookups/minute. It does not name a sibling alternative (e.g. linkedin_get_connections) for the case where the caller wants their own list, so it stops short of full when/when-not guidance.

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