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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful operational facts — a cost of 5 credits and the required Authorization: Bearer header — which go beyond the schema. It omits pagination behavior, result volume limits, and rate/error handling, leaving real gaps for a read tool.

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?

Purpose is front-loaded in the first clause and the boilerplate (platform, resource, cost, auth) is compact. Minor blemishes: a doubled period after 'metadata' and template-style key=value phrasing that reads as generated filler.

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 usefully names the return fields, and it covers the two operational essentials (cost, auth). For a single-parameter read tool that is close to sufficient; only pagination/limit behavior is unaddressed.

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% with a single 'url' parameter already documented and exemplified in the schema. The description adds no syntax or format detail beyond that, so the schema does the work and 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 ('Discover recent public posts from a LinkedIn company page URL') plus the returned fields (text, engagement, author metadata). An agent can distinguish it from linkedin_post (single post) and linkedin_company (profile) by the resource noun, 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?

The description says what it returns but never states when to choose it over linkedin_post, linkedin_company, or linkedin_job, nor any prerequisites beyond auth. The only implicit guidance is the word 'public', which hints at scope but is not framed as a usage rule.

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