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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a meaningful behavioral constraint beyond the annotations: the tool only works on the authenticated user's own posts. It does not mention auth scopes, rate limits, or return shape beyond metric names, so it is not a 5.

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?

Two sentences, both front-loaded and information-dense. The metric list is stated first and the ownership restriction follows, with no filler or redundancy.

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 compensates by enumerating the metrics returned (impressions, reactions, comments, reshares, CTR, engagement rate) and states the critical ownership constraint. Combined with full schema coverage for both parameters and read-only annotations, an agent has everything needed to call it correctly.

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 100%, with the 'post' parameter documenting accepted URL/URN formats and 'include_demographics' documented with a default. The description does not add syntax or format details beyond the schema, so the baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific verb ('Returns'), the resource ('engagement metrics... for one of your own LinkedIn posts'), and enumerates the exact metrics returned. It clearly distinguishes itself from siblings like linkedin_get_post_comments or linkedin_get_post_reactions by being a metrics tool scoped to the caller's own posts.

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?

It gives a clear usage context and an explicit exclusion: only posts authored by the connected account, and analytics for other users' posts are unavailable. However, it does not name an alternative tool or suggest what to use when the post is not yours, so it falls short of a full when/when-not/alternatives statement.

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