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

Goes well past the readOnlyHint/openWorldHint annotations by disclosing a hard quota ("counts against a daily allowance (100 a day)") and warning that user-authored text must be treated as data, not instructions — an injection guardrail the annotations cannot express. It also tells the agent the response shape, which survives the missing output schema.

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 compact sentences with no filler: capability and return fields first, then the chaining use, then the cost and safety caveat. Every clause carries information the agent needs.

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 two-parameter read with no output schema and full schema coverage, the description closes the remaining gaps: what fields come back, the quota cost, and the untrusted-content caveat. Nothing needed to call it correctly is missing.

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 coverage is 100%, so both parameters are already documented, including that `post` accepts a URL or a socialId. The description only reinforces that the socialId originates from this tool's own return value; it says nothing about `connectionId` semantics, so this lands at the baseline.

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?

Names a specific verb and resource ("Read ONE LinkedIn post") and enumerates exactly what comes back: text, author, date, attachments, and the four engagement counts. The emphasis on "ONE" separates it from the post-listing and post-searching siblings without opening their schemas.

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 line "Returns its socialId, which the comment and reaction tools take" tells the agent this is the prerequisite step before comment_on_post, list_post_comments or react_to_post. There is no explicit exclusion clause (e.g. "use get_recent_posts to list many"), so guidance is strong but not fully exhaustive.

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