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 two important operational facts an agent needs: a 2-credit cost and the required 'Authorization: Bearer <api_key>' header. It omits error/edge-case behavior (private, deleted, or rate-limited requests) which matters for a paid external fetch.

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 core sentence is front-loaded and efficient, but the appended boilerplate 'Platform=linkedin resource=post.' is redundant with the tool name and adds no value, and there is a stray double period ('metadata..'). It is short but not maximally economical.

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 enumerates the returned fields (text, likes, comments, author metadata), so an agent knows what to expect. Auth and cost are covered; the remaining gap is edge-case handling for non-public or invalid URLs.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents 'url' with an example. The description adds only the phrase 'by URL', which restates the schema rather than extending it. Baseline 3 is appropriate.

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 (Fetch) and resource (public LinkedIn post by URL) and enumerates the payload (text, likes, comments, author metadata). The resource ('post') is distinct from the LinkedIn siblings linkedin_company and linkedin_job, though no alternative 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?

'Fetch a public LinkedIn post by URL' implies the usage context and quietly signals the public-post limitation. There is no explicit when-to-use guidance, no statement about private/deleted posts, and no routing to alternative tools for feed or company data.

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