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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is clear. The description usefully adds that results are sorted by most recently added, but it does not add other behavioral context such as privacy scope or pagination semantics.

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?

The description is a single front-loaded sentence with no wasted words. It states the core action and sorting behavior efficiently.

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 simple read-only list tool with fully documented parameters and explicit annotations, the description is nearly complete. It gives the action and sort order, though it could mention return shape or pagination behavior more directly; however, the schema's cursor field already covers pagination.

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 the parameters—limit, cursor, in_workspace, and from_account_id—are fully described in the schema. The description adds no parameter-level meaning beyond what the schema already documents, 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?

The description states a specific verb and resource: list your LinkedIn connections. The phrase 'sorted by most recently added' adds a clear behavioral detail. It is distinguishable from siblings like linkedin_search, linkedin_list_invitations_sent, and linkedin_list_reactions because it targets the user's existing connections.

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 description implies the tool's use case by saying 'List your LinkedIn connections,' but it does not explicitly say when to use this versus alternatives such as linkedin_search or linkedin_list_invitations_sent. No exclusions or alternative routing guidance are provided.

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