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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond that: it clarifies the result set is a mutual-connection intersection and states results are paginated via cursor, which tells the agent to expect multi-page reads.

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 sentences, front-loaded with the core action and scope, followed by use case and pagination note. Each sentence carries information and none is padding.

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 two-parameter, read-only, no-output-schema tool, the description covers scope, accepted identifier forms, and pagination — enough to invoke correctly. It could still note behavior when no mutual connections exist or when the target is unreachable, which leaves a small gap.

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 100%, so both the identifier formats and the cursor semantics are already fully documented in the schema. The description's mention of URL/public ID/URN duplicates that content without adding syntax or constraint detail, so 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?

The description states a specific verb and resource ("List the mutual (shared) connections") and immediately scopes it as being between you and a target profile, which is exactly what separates it from the sibling linkedin_get_connections. The parenthetical definition of shared connections removes any ambiguity about the returned set.

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?

It gives a concrete reason to reach for this tool ("finding who can give a warm introduction"), which is real usage context. It stops short of naming alternatives or exclusions — e.g. that linkedin_get_connections returns your full network, or that target-network-only data comes from a different sibling — so an agent must infer the boundary.

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