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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that—no pagination behavior, rate limits, or result-ceiling details despite an offset parameter existing.

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 short sentences, front-loaded with the scope and then the key calling convention. Tight, though the second sentence partly duplicates the schema's user_id description.

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 says nothing about return shape or pagination, which matters for a list tool with an offset parameter. Annotations cover the safety profile, so the gap is moderate but real.

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 67%: user_id and account_id are richly documented in the schema, while offset is undocumented in both places. The description's 'me' tip largely restates the schema default/description, so it adds only marginal value.

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?

Specific verb 'List' with resource 'followers' and explicit scope (account owner or a known LinkedIn user). The directionality (followers vs following) is implicitly clear against the sibling linkedin_list_following, though that sibling is never named.

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 sentence about user_id='me' is parameter guidance rather than when-to-use. It implies the listing use case but gives no when-not conditions and never routes to alternatives like linkedin_list_following.

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