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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is fully covered. The description adds the workflow purpose (supplying post_id) but says nothing about pagination behavior despite an offset parameter, or the shape of the listing returned.

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 tight sentences, zero filler, with the action and the downstream-use guidance front-loaded. Nothing is wasted or buried.

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 should ideally convey the return shape and pagination. It mentions post_id, which is the key output, but leaves offset/pagination and the listing format unspecified, so an agent still lacks full context.

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 carry detailed schema descriptions, but offset has none. The description restates the source options ('connected LinkedIn user or a known provider user ID') but adds no syntax or format beyond what the schema already provides. Baseline 3 fits.

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 with scope: 'List posts authored by the connected LinkedIn user or a known provider user ID.' This distinguishes it from linkedin_get_post (single post), linkedin_search_posts (search), and linkedin_resolve_my_post, so an agent can route correctly without opening 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?

Explicitly frames the workflow: 'Use to locate a recent post and obtain its post_id before reading comments/reactions or replying.' This gives clear when-to-use context and downstream alternatives. It stops short of stating when-not to use it, so not a full 5.

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