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

Annotations already declare readOnly=false, destructive=true, openWorld=true, and idempotent=false, so the write/irreversibility profile is covered. The description adds useful detail on accepted identifier formats and the 300-character message cap, but says nothing about rate limits, duplicate/pending-request behavior, or auth needs that annotations don't already imply.

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 tight sentences, front-loaded with the core action and with no filler. It is appropriately sized, though the identifier-format sentence slightly duplicates the schema.

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 no output schema and a mutation tool, the description does not state what the agent should expect on success or failure (e.g., pending vs. failed request), nor how it relates to manage/list connection request siblings. It is adequate for invocation but leaves behavioral gaps for a destructive, non-idempotent action.

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%, so both parameters are fully documented in the schema, including identifier formats and the 300-character limit. The description largely restates this, adding no syntax or format meaning beyond what the schema already provides, so the 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 ('Send a LinkedIn connection request to a person'), which is unambiguous. However, it does not differentiate itself from the sibling linkedin_manage_connection_request, which likely also touches connection requests, so an agent must infer the split.

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?

No when-to-use guidance is given. There is no mention of when to prefer this over linkedin_manage_connection_request (e.g., for accepting or withdrawing), nor any prerequisite such as being logged in or not already being connected. Usage is only implied by the verb 'send'.

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