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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true), yet the description adds genuinely non-obvious behavior: the feed is ranked by LinkedIn and shifts between calls, so offsets must not be cached; pagination is cursor-driven via next_start/pagination_token; and there is a practical rate constraint ('one LinkedIn call per page; keep to a few pages per run').

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 but front-loaded: what the feed is, what it contains, what's excluded, then pagination, then when to use vs. the alternative. The trailing 'Read-only' is redundant against readOnlyHint, and a couple of clauses restate the same scoping idea, but almost every sentence carries information.

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 an output schema present, return values need no explanation, and the description still covers what the caller must know: items per page, pagination contract, feed volatility, exclusions, and downstream actions. Nothing needed to call this correctly appears to be 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 100%, so the baseline is 3, but the description adds sequencing semantics beyond the schema: 'First call with start=0; for the next page pass back next_start and pagination_token,' plus the warning against reusing offsets. That explains how the three parameters relate rather than just what each is.

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+resource (read the account's LinkedIn home feed) and pins down scope precisely: recent posts from connections and followed people/pages, plus feed_reason items, excluding ads and suggestion carousels. It also distinguishes itself from siblings by naming search_posts for topic-wide search and list-oriented tools implicitly via the 'people the account already knows or follows' framing.

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 says when to use it (finding posts to engage with among known connections/followed creators) and when not to (for a topic across all of LinkedIn, use search_posts). It also chains the workflow forward: 'Then like_post or comment_post with post_urn.'

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