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 fully covered without the description. The description adds result-shape context (platform/content-type breakdown, top posts, daily trend), which is useful, but discloses no behavioral traits such as rate limits, auth requirements, or how 'top posts' are ranked.

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 tight sentences, front-loaded with the scope and then the breakdown contents; nothing is wasted. The leading 'Group analytics' header is a minor restatement of the tool name, which keeps it just below a 5.

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 analytics tool with full schema coverage and safety annotations, the description supplies the aggregation scope and a sketch of the return contents (platform, content type, top posts, daily trend), which is valuable given there is no output schema. It stops short of naming the sibling tools or clarifying cost/pagination behavior.

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 limit, period, postsLimit and groupId all documented in the schema itself (including the limit/postsLimit alias precedence rule). The description adds no parameter-level meaning, so the baseline 3 is appropriate.

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 states a specific verb+resource ('Aggregate social performance analytics for all posts in a content group') and scopes it to a group, which implicitly distinguishes it from getPostAnalytics (single post) and getAnalyticsOverview (account level). It never names those siblings explicitly, so the differentiation is left to inference.

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?

Usage is only implied by the scope phrase 'all posts in a content group'; there is no explicit when-to-use, when-not-to-use, or pointer to getPostAnalytics/getAnalyticsOverview/refreshAnalytics. An agent can infer the right context from the scope, but nothing is stated.

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