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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closedWorld, so the safety profile is covered. The description adds only the 'pending' qualifier; it says nothing about pagination behavior, result caps, or whether multiple LinkedIn accounts merge results, which the four-parameter surface would benefit from.

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?

A single front-loaded sentence with no filler; the scope-defining word 'pending sent' appears before the resource. Nothing to trim and nothing repeated from structured fields.

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 4 optional parameters, no output schema, and annotations covering the safety profile, the description is minimally sufficient to invoke the tool. It is, however, thin on multi-account and pagination behavior that an agent must reason about from the schema 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 100% and each parameter (limit, cursor, in_workspace, from_account_id) is documented in-schema. The description contributes no additional parameter meaning, 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 specific verb (list) and a specific resource (pending sent connection invitations on LinkedIn), which is enough to separate it from linkedin_invite (sends one) and linkedin_list_connections (accepted connections). It does not name those siblings explicitly, so it stops short of full differentiation.

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 word 'pending sent' implies the use case (checking outbound invites not yet accepted), but there is no explicit statement of when to prefer this over linkedin_invite or linkedin_search, and no prerequisites or exclusions. Usage is inferable rather than stated.

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