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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description earns credit for adding a genuine data-quality caveat — 'No available metrics is missing data, not proof of zero performance' — which changes how an agent should interpret empty results. It omits anything about freshness/sync timing (relevant given a refreshAnalytics sibling) or result size.

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 short blocks, front-loaded with the purpose and then the payload contents plus caveat; every sentence contributes. The opening line duplicates the annotation title verbatim, which is mildly redundant but functions as a headline.

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 usefully enumerates what comes back (platform totals, top posts, follower counts, daily trends) and warns about absent metrics. What's missing is any treatment of the period parameter or data-freshness expectations for an analytics read.

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 0%, so the description carries the burden for the single 'period' enum parameter, and it says nothing about it — no window semantics, no interaction with 'daily trends' granularity, no hint that the ranges are capped at 90d. The enum values are largely self-explanatory, which keeps this above a 1.

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 (compare/read) and resource (social performance) and scopes it to all content groups, which distinguishes it from per-group/per-post siblings like getGroupAnalytics and getPostAnalytics. It stops short of naming those siblings explicitly, so an agent must infer the boundary.

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?

Scope wording ('across all your content groups', 'compare across brands') implicitly signals this is the aggregate/cross-brand view rather than the per-group or per-post analytics tools. However, there is no explicit when-to-use statement, no exclusion of the sibling analytics tools, and no prerequisite guidance.

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