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

With no annotations, the description carries the full burden and does well: it discloses metered cost (5 credits per page of 50, capped at 250 posts, charged only for pages actually fetched) and a real side effect — results persist into the post library with source_type='external' and a linked linkedin_profiles row. It omits auth requirements and whether re-fetching duplicates stored rows, which keeps it below 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?

Three compact sentences with zero waste: purpose first, then cost, then the persistence side effect. Every clause carries information an agent would otherwise have to guess.

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?

Covers scope, pricing, and the write side effect for a tool with no annotations and no output schema. The remaining gap is the return shape — what fields a post carries and how 'recent' is bounded — which is not covered anywhere else since there is no output schema.

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 description coverage is 100%, so all three parameters are already documented in the schema, including refresh's cache semantics and max_posts' range. The description only reinforces the 250-post ceiling and per-page credit pricing, adding little beyond the structured fields — the baseline 3 applies.

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 — 'Fetch recent posts from a LinkedIn company page' — which cleanly separates it from the profile-oriented sibling (linkedin_profile_posts) and from linkedin_post_search. It does not explicitly name an alternative tool, so it falls just short of the top mark.

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?

The company-page scope implies when this tool applies, and the credit model gives an agent enough to weigh whether a fetch is worth it. However, there is no explicit 'use X instead when...' routing and no stated prerequisites (e.g. that a linkedin_url must resolve to a company page).

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