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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered. The description adds genuinely useful behavioral detail the annotations lack — the 7-day default window and the semantics of media_type being absent when the format cannot be determined.

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, front-loaded with the resource and returned fields; the second sentence adds the creative-reuse purpose without padding. Slightly loose in the trailing clause but no wasted sentences.

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?

An output schema exists, so return shape need not be explained. For a read-only analytics tool the description covers scope, metrics, default window, and purpose adequately; only the sibling-overview distinction 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 description coverage is 100%, so defaults, 90-day cap, and pagination are already documented in the schema. The description only restates the 7-day default and adds no date-format or cursor semantics beyond what the schema gives, so baseline 3 applies.

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 (list) and resource (per-post LinkedIn analytics) and enumerates the returned metrics plus media_type, so the scope is unambiguous. It does not explicitly contrast itself with the sibling get_analytics_overview, though 'per-post' vs an overview is reasonably inferable.

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?

Provides clear context for use: default 7-day window when no range is given, and a concrete job to be done ('find top-performing posts and reuse the topics, formats, and hooks'). It never states when not to use it or points at get_analytics_overview as the account-level alternative, so no exclusion guidance.

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