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

Annotations already cover safety (readOnlyHint, destructiveHint false), and the description adds non-obvious behavior beyond them: the 100/day daily allowance (a rate limit) and an explicit prompt-injection warning that names, headlines, messages and post text are untrusted data. Both are high-value traits an agent cannot infer from annotations.

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?

Front-loaded and dense but every sentence earns its place: mode selection, output shape, rate limit, injection caution. The bracketed id-convention preamble is compact though slightly cryptic in its shorthand.

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, the description compensates by naming the returned fields (followers[].id, followers[].profileUrl) and the count limit. Together with the schema it covers scope, pagination, rate limits and safety — nothing an agent needs is missing.

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 already 100%, so the baseline is 3, but the description adds cross-tool linkage ('from get_profile_details → providerId') and the output id mapping that the schema does not supply. It also clarifies the semantic distinction between member id and company numeric id.

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 who follows you on LinkedIn') and immediately distinguishes the two modes: your own followers by default vs. another member or company page via `of`. An agent can tell it apart from siblings like list_connections or get_post_engagers without opening the schema.

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?

Clear context for when to supply `of` (someone else's followers, member id or company numeric id). It does not name an alternative tool or an explicit when-not-to-use condition, so it falls just short of full routing guidance.

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