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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so 'Read-only: returns public data and changes nothing' mostly restates them. However, the description adds genuinely new and operationally important behavior not present in the annotations: a cost of 1 credit per result with a minimum of 1 credit per request, which directly affects how an agent should size the count parameter.

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 short sentences with the purpose front-loaded and cost information placed immediately after, so the agent reads the important constraint before calling. The read-only sentence is partly redundant with the annotations, which is the only wasted text.

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?

With no output schema, the description never indicates what a returned post contains (text, timestamps, engagement counts, pagination cursor behavior), and 'returns public data' is too vague to fill that gap. For an otherwise simple, well-annotated list tool with fully documented parameters, the missing return-value framing is the main shortfall.

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%, and the schema already documents count (1-100, default 10), start (skip offset) and universalName (accepting either a short name or a full LinkedIn URL). The description adds no parameter meaning beyond that, so 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?

The description gives a specific verb and resource: 'List posts published by a LinkedIn company', which is clearly distinct from linkedin_get_posts_from_profile and linkedin_search_posts by entity type. It does not explicitly name those siblings, so it stops short of full differentiation.

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 is only implied: an agent can infer this is the tool for pulling posts from a known company, versus linkedin_get_post_detail for a single post or linkedin_search_posts for discovery. There is no explicit when-to-use or when-not-to-use guidance, nor any stated prerequisite (e.g., needing a company identifier rather than a person).

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