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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description adds real context beyond them: cache-first serving, the cost tradeoff of refresh:true, automatic live refresh when the cache is empty/stale, and the legacy-vs-live-sender behavioral difference. It stops short of stating rate limits or pagination semantics, so it earns a solid 4 rather than a 5 against the annotation baseline.

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?

Dense and front-loaded, leading with the resource and then the operational details. The bracketed 'Ids in: none. Ids out: connections[].profileUrl: profile link.' fragment is cramped and partially duplicates the return-summary sentence later, which is minor waste rather than a structural flaw.

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?

No output schema exists, and the description compensates by enumerating the returned fields (name, profileUrl, headline, connectedAt) per person. Combined with the safety annotations covering the read profile, an agent has everything needed to call and interpret this tool.

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 the baseline is 3, but the description adds meaning the schema does not: that 'since' covers when the connection was made, that search matches name or headline, and the cache-staleness rule behind refresh:false. The 'Ids in/out' preamble is largely redundant with the schema.

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 and resource: 'List the connected LinkedIn account's own 1st-degree connections', with the crucial qualifier 'people you're connected WITH' to distinguish it from invitations/followers. It reads clearly against siblings like list_followers, list_received_invitations and search_linkedin_people without needing their schemas.

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?

Gives explicit use cases ('who am I connected to', segmenting your network, first step of a custom workflow) and names the alternative sibling connections_never_messaged for the pre-joined variant. Also documents the refresh condition for switching between cached and live modes, so the agent knows when to set that flag.

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