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

readOnlyHint=true already establishes the safety profile, so credit goes to what the description adds: a hard cap of five posts, that metrics are lifetime (not date-bounded), that clicks/shares only exist for Pages, and the precondition that a personal profile's posts must have been published through Adeli. That last item is a real failure mode an agent would otherwise hit at call time.

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 sentences, each earning its place: the first front-loads what is returned and the scope limit, the second covers the primary parameter, and the third flags a constraint. No filler or restatement of the title.

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 carries the burden of describing returns and it does so by naming the metric families. The one remaining gap is response structure per post (how metrics are keyed or shaped, and whether absent metrics are omitted), which is minor for a read-only metrics tool but not fully closed.

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 the baseline is 3, and the description goes beyond it by explaining the format ('comma-separated list of post URNs'), giving concrete URN variants (urn:li:share / urn:li:ugcPost), naming the upstream source (create_post's providerId), and stating the omit-for-recent-posts behavior for postUrns. profileId is left entirely to the schema, which is acceptable given full coverage.

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 ('Return') and enumerates exactly which metrics come back ('lifetime impressions, reactions, comments and, for Pages, clicks and shares') scoped to 'up to five LinkedIn posts'. The post-level scope clearly separates it from the sibling get_linkedin_account_insights without the agent needing to open a schema.

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?

Tells the agent two concrete usage paths: pass postUrns to target specific posts (with an example of where those URNs come from, create_post's providerId) or omit it to get the account's recent posts. It does not explicitly name a competing sibling such as get_linkedin_account_insights as the account-level alternative, so the routing guidance is clear but not exhaustive.

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