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

Adds real context beyond the readOnlyHint annotation: it discloses what comes back (velocity over time, LinkedIn reaction-type split, per-network metrics such as discussion rate, profile viewers, saves, sends, follows) — valuable since there is no output schema. The trailing 'Read-only' merely restates the annotation, and it says nothing about behavior when a post isn't found or has no data yet.

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?

Front-loaded with purpose and return shape, then identification mechanics; the example questions are compact and concrete. Slightly padded by the redundant 'Read-only' sentence and by naming individual metric types that could have been summarized as 'all tracked per-network metrics (examples: ...)'.

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 and four all-optional parameters, the description is exactly what's needed: it explains how to select a post, what the response contains, and that platform is a modifier rather than a standalone selector. Nothing an agent needs in order 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 baseline is 3; the description adds meaning by explaining that post_id, composition_id and latest are alternative identification paths and that platform only narrows `latest` — a constraint the schema hints at but doesn't enforce or explain. All parameters are optional with nothing required, and the description makes clear that one identifier must be chosen.

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?

Opens with a specific verb+resource and scope: full metrics for ONE post, plus time-series velocity. That single-post scope is exactly what separates it from get_analytics_summary and list_posts_with_metrics in the sibling list, so an agent can route without opening 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?

Gives concrete user-question triggers ("how did my last post do?") and spells out three distinct identification paths, naming the sibling that supplies each id (list_top_posts, list_drafts). It lacks an explicit 'not for aggregate/account-level reporting — use get_analytics_summary' exclusion, which is the one ambiguity left.

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