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

With readOnlyHint and openWorldHint already declared, the description adds useful behavioral context: it lists returned content, notes that top-level comments appear in `raw.comments`, and states the cost of 1 credit. It does not cover cache behavior or rate limits, but the extra return-shape and cost details are substantive beyond the annotations.

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 description is front-loaded with the purpose, then efficiently lists return fields, special comment behavior, and cost. Every sentence adds information without waste.

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?

For a simple read-only retrieval tool, the description covers the returned payload and notes where comments appear. However, it leaves the `cache_max_age` parameter unexplained and does not route the agent away from related LinkedIn transcript or search tools.

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 only 50%, and the description does not explain the `url` format or the optional `cache_max_age` parameter. Since one of the two parameters is undocumented in both schema and description, the description fails to compensate for the coverage gap.

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 clearly identifies the resource as a single LinkedIn post and enumerates the returned fields: full text, media, author, publication time, reactions, and comment count. It distinguishes this from broad post-list siblings by specifying 'One LinkedIn post,' though it does not explicitly contrast with linkedin_postTranscript or linkedin_searchPosts.

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 does not state when to use this tool versus alternatives such as linkedin_postTranscript or linkedin_searchPosts. It provides only an implied use case: retrieving details for one post, without exclusions or sibling routing guidance.

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