List LinkedIn Connections

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds valuable behavioral context beyond annotations: pagination ('one cursor page'), visibility scope ('visible'), and the explicit non-search behavior, which helps set expectations.

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?

Two short sentences carry all key information without redundancy. The purpose and primary behavior are front-loaded, and every word contributes meaning.

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?

Given the output schema exists and annotations cover safety, the description is fairly complete: it defines the resource, pagination, visibility, sort behavior, and exclusions. It falls short only in not naming the search alternative and offering little help for required parameters, but overall the context is solid for a list operation.

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 only 17%, so the description must compensate, but it does so minimally. It mentions 'cursor page' (cursor) and 'sort order' (sort_by), yet leaves required params (context_id, request_id) and page_size semantics unexplained. The description does not provide enough parameter-level meaning for such low schema coverage.

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 uses a specific verb ('List') and clearly identifies the resource ('first-degree connection inventory') while also stating its scope ('visible', 'selected visible sort order'). It explicitly distinguishes itself from the search tool by saying 'This tool does not search,' which is a strong differentiator given the sibling tool 'linkedin.connections.search'.

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?

The phrase 'This tool does not search' provides an exclusion that signals when not to use this tool, but it does not explicitly name the alternative ('linkedin.connections.search'). It also implies pagination usage with 'one cursor page,' giving some contextual guidance for iterative fetching.

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