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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context by specifying that only pending requests are returned and that the output supplies the request_id used by follow-up mutation tools, which is useful behavioral context beyond the annotations.

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 sentences with no filler. The purpose is stated first, then the actionable usage context, and every clause contributes to correct invocation.

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 listing tool, the description covers the operation, the required type parameter, and the downstream use of request_id. It could be more complete by hinting at the response shape or pagination, but nothing essential for a safe call is missing.

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 50%; the rich account_id guidance is already in the schema, and the 'sent or received' wording adds minimal meaning beyond the enum on the required 'type' parameter. The description does not substantially compensate for the enum parameter having no schema-level description, but the enum itself is fairly self-explanatory.

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 names a specific verb ('List'), a specific resource ('pending LinkedIn connection/relation requests'), and a clear scope ('sent or received by the account owner'). This clearly distinguishes it from adjacent invitation tools like linkedin_accept_invitation and linkedin_cancel_or_refuse_invitation.

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 explicitly tells the agent when to call this tool: before accepting/refusing a received invitation or withdrawing a sent one, in order to obtain the request_id. It provides clear context but does not explicitly state when-not-to-use or name alternative listing tools.

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