linkfetch_get_company_posts

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses almost nothing beyond the name: no auth/credential requirements, no rate-limit or quota behavior, no pagination semantics, and no definition of what 'recent' means. Only the read-only nature is implicit in the verb 'get'.

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?

A single front-loaded sentence fragment with zero filler; the resource and the keying parameter are both stated in the first clause. It is efficient, though so terse that it borders on under-specification.

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?

There is no output schema and no annotations, so the description is the only place to explain return shape, ordering, and pagination interaction ('recent' with limit/offset). For a simple 3-param read tool with full schema coverage this is minimally acceptable, but 'recent' is left undefined and no behavioral context is supplied.

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 slug, limit, and offset are all documented in the schema itself. The description only echoes the slug requirement ('by company slug') and adds nothing about pagination behavior or ordering, so it hits the baseline of 3 without exceeding it.

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 (get/list), resource (posts), and scope (published by a LinkedIn company page), which separates it from the profile-posts and single-post siblings. It never names those siblings explicitly, so differentiation is inferable rather than stated.

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 description implies you call this to read a company page's posts, but gives no when-to-use condition, no exclusions, and no pointer to alternatives such as linkfetch_get_profile_posts, linkfetch_search_posts, or linkfetch_get_post. An agent must open the sibling schemas to route correctly.

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