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

Annotations already establish that this is safe, idempotent, open-world reading, so the description's added details about partial failures via data.errors and the LINKEDIN_BATCH_UNAVAILABLE/INSUFFICIENT_SCOPE recovery path are meaningful beyond the structured metadata. It also clarifies that includeEngagement changes the response by adding comment and reaction summaries.

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 compact and front-loaded: purpose first, then parameter guidance, error handling, and recovery instructions. Every sentence contributes operational information without repetition.

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 batch-read tool with no output schema, the description covers the key operational concerns: input sourcing, batch size, engagement inclusion, partial failures, and permission-error recovery. Return-shape details beyond data.errors are omitted, but that is a minor gap.

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?

With only 50% schema description coverage, the description compensates well: it identifies the source of connectionId, explains that postedIds are share or ugcPost URNs, and gives includeEngagement a concrete meaning. workspaceId remains unexplained beyond its schema pattern, which keeps it from a 5.

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 states a specific verb ('Read'), resource ('published posts from one LinkedIn Company Page'), scope ('up to 50 known'), and platform constraint ('Standard app'). The word 'batch' and 'known published posts' distinguish it from sibling list tools such as company_list_linkedin_page_posts.

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 explains how to source the connection ID and what URN types to supply, and it describes retry behavior for specific errors. It does not explicitly contrast when to use this batch tool versus company_list_linkedin_page_posts or company_get_post, but the batch/known-post framing gives enough context.

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