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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds meaningful context about target scoping and what the computation produces (averages, totals, best-performing posts). It does not discuss rate limits, latency, or caveats on sparse data, but for a read-only aggregate that is minor.

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, no filler, and the core capability is front-loaded before the scoping detail. 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 read-only statistic tool with no output schema, the description gives a usable picture of the returned content (averages, totals, best-performing posts) and the target scoping. Only the precise shape of 'best-performing' and date-range defaulting remain unspecified.

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 all three parameters including the ISO 8601 date formats and the organization id/urn/name forms are documented in the schema itself. The description only restates the organization override and adds a cross-reference to list_organizations, so the 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?

States a specific verb and resource ('computes a statistical summary of LinkedIn posts') plus the scope ('over a given period'), which clearly separates it from list_posts and get_post. An agent can identify it as an aggregate-analysis tool without opening the 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?

Specifies the default target (personal profile) and the condition for the alternative target (pass `organization` for a company page), pointing to list_organizations for the id. It does not say when to prefer this summary over list_posts or search_posts, so it stops short of full when/when-not guidance.

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