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

Annotations already declare readOnly=false, idempotent=false, openWorld=true, destructive=false, so the safety and mutation profile is covered. The description adds essentially nothing behavioral beyond that — it doesn't explain that the call is non-idempotent (repeat sends create duplicates), whether a note consumes connection-request quota, or what happens when a request is already pending. The identifier and 300-char details it does add are parameter-level, not behavioral.

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 short sentences, front-loaded with the action and followed by input and optional-message constraints; nothing is padded. Slight redundancy with the schema's own parameter descriptions keeps it from a 5.

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 2-parameter mutation with no output schema, the essentials are covered, and the lack of return-value explanation is acceptable here. What's missing is guidance an agent needs before firing a non-idempotent, open-world write: no note on duplicate sends, quota/permission prerequisites, or how it relates to linkedin_manage_connection_request.

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%, so both parameters are fully documented in the schema, including the URL/slug/URN formats and the 300-character message limit. The description merely restates those same facts, adding no syntax, format, or edge-case meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

Clear verb+resource ('Send a LinkedIn connection request to a person'), and it specifies the operation is a single-request send rather than a bulk or list operation. However, it does not differentiate itself from the sibling linkedin_manage_connection_request, which plausibly covers accept/withdraw/other request actions, leaving ambiguity an agent must resolve by schema inspection.

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?

Usage is implied by the name and the identifier guidance, but there is no explicit when-to-use, no exclusions, and no routing to alternatives such as linkedin_manage_connection_request (for other request actions) or linkedin_send_message (for messaging existing connections). An agent gets context but no decision guidance.

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