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

With readOnly/openWorld/non-destructive already declared in annotations, the description still adds real value: nullable activityUrn/contentUrn, comments being a public preview with no pagination, Pulse article previews possibly returning null dates and reaction counts, and per-request cost with repeat purchases. That is undercut by muddled pricing text that says both 'at least 10 Nexscope credits' and '1 credit per request', leaving the agent unsure of actual cost.

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 return-field detail is front-loaded and useful, but the text is padded with pasted pricing/marketing boilerplate ('View Pricing', 'Actual supplier units are reported per request', 'Examples are not guaranteed prices') and repeats the comment-preview limitation twice. Roughly a third of the text is vendor noise rather than tool guidance.

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 correctly shouldered the burden of describing return values and did so thoroughly, including nullability and the comment-preview limitation. It is only short on error/edge behavior (invalid or non-LinkedIn URL) and on clarifying the conflicting credit cost.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries the load and a 3 is the baseline. The description adds no input-side meaning such as accepted URL forms (feed post vs Pulse article vs activity URN), which would have been the one useful addition here.

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 opening sentence names a specific verb and resource ('Fetches a single LinkedIn post or article') and immediately enumerates the returned fields, so an agent knows this is a single-item detail lookup rather than a search. The 'single post' framing implicitly separates it from sibling list/search tools like social_linkedin_search_posts and from the transcript variant.

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: it takes one URL and returns one post's detail, which suggests 'use when you already have a post URL'. There is no explicit when-to-use/when-not guidance and no sibling is named (search_posts, post_transcript, company_posts are all plausible alternatives left unaddressed).

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