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

Annotations already cover read-only/idempotent/open-world safety, and the description goes further by disclosing ordering (newest first), organic-only stats, pagination via start/next_start, total semantics, and the cost signal "one LinkedIn call per page of posts." The trailing "Read-only" merely restates the readOnlyHint, and error/limit behavior is not discussed, so it stops short of a 5.

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-loads the core action and scope, then the payload, then downstream routing, then pagination — a sensible order with no filler sentences. The long run-on field enumeration (nine metrics plus six metadata fields) is dense and could be tightened, but each clause carries information an agent needs.

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 4-parameter read tool with an output schema and full annotation coverage, this is close to complete: ordering, stat scope (organic only), pagination, call cost, and downstream hand-off are all covered. Minor gaps remain around failure modes (e.g., missing read_analytics) and whether next_start/total appear alongside the listed fields, which the description references but never frames as return values.

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 count/start/page_id/account_id are already documented, giving a baseline of 3. The description adds meaning the schema lacks: pagination is a start/next_start contract, page_id must be reused verbatim downstream with post_urn, and total represents the page's post count — useful operational semantics beyond the field definitions.

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+scope: a company page's own posts, newest first, mirroring the admin Posts tab, with an explicit field inventory (impressions, engagement_rate, post_urn, author_linkedin_id). This clearly separates it from siblings like list_user_posts, scrape_my_posts, search_posts and list_page_activity.

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?

Gives two concrete use cases (measuring page post performance; picking a post to engage on) and routes the agent forward explicitly: "then scrape_post with post_urn for who engaged," and states post_urn can go as-is to comment_post/like_post with the same page_id. The alternative and its selection condition are named rather than inferred.

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