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

Beyond the readOnly/openWorld annotations, the description discloses the hard 7-page platform limitation and warns that repeated requests may purchase data again — genuinely useful behavioral context for a paid read tool. It loses a point because the cost statements conflict with each other ('at least 10 Nexscope credits' vs '1 credit per request'), leaving pricing ambiguous.

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 first half is well front-loaded, but the remainder is scraped pricing boilerplate: 'LinkedIn Company Posts API View Pricing', a duplicated 'Limited to 7 pages by LinkedIn', and two contradictory credit figures. These sentences do not earn their place and actively confuse.

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 two-parameter read tool with no output schema, the description covers return fields, URL formats, pagination ceiling, and cost awareness. The only real gap is the unresolved credit contradiction, which an agent would need to resolve to reason about cost.

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 both parameters are already documented; the description still adds meaning by capping `page` at 7 due to a LinkedIn limitation, which the schema does not express. It adds nothing new for `url` beyond the example already in the schema.

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 opening sentence gives a specific verb and resource — retrieves paginated posts from a LinkedIn company or school page — and enumerates the returned fields (URL, ID, publication date, full text). Scope is unambiguous relative to the social_linkedin_company sibling, though no sibling is named explicitly.

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?

Usage context is implied by the accepted URL forms (/company/ and /school/) and the 7-page cap, but the description never says when to pick this over social_linkedin_company (profile data) or social_linkedin_search_posts (keyword search). No exclusions or prerequisites are stated.

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