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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds a behavioral caveat about provider restrictions, but it does not disclose pagination behavior or result format, and with no output schema some behavior remains implicit.

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?

The description is two short, purposeful sentences with no filler. The main action is front-loaded, and the usage caveat follows immediately.

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 list tool, the schema carries the heavy parameter guidance and the description gives the key scope and provider caveat. The main gap is the undocumented offset parameter and lack of explicit comparison to linkedin_list_followers, but nothing essential is missing for a routine call with user_id=me.

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?

The schema already provides rich, detailed descriptions for user_id and account_id, and the description reinforces the user_id default with prefer user_id=me. However, offset has no description in the schema or the tool description, and the description does not explain its pagination usage, so it only partially compensates for the 67% schema coverage.

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 opens with a specific verb and object: it lists LinkedIn users followed by the connected account owner. This unambiguously distinguishes the tool from sibling linkedin_list_followers by direction, and the follow-up preference for user_id=me reinforces the intended scope.

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?

It gives clear context by instructing the agent to prefer user_id=me and warns that provider availability may restrict data for other users. It does not explicitly name when-not-to-use cases or alternatives such as linkedin_list_followers, so it misses the top bar by a small margin.

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