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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is fully covered without description help. The description adds the useful fact that output is a per-day series of specific metrics, but says nothing about timezone, whether gaps are filled, or how the period affects the series.

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?

A single short sentence with zero padding, and the metric list is front-loaded. It is a fragment rather than a sentence with a verb, but nothing is wasted.

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 one-optional-parameter read tool with full annotations and no output schema, the essentials are nearly covered, but the description should at least state that results are returned for the selected period as a daily series and hint at the shape of each data point. It partially does so via the metric enumeration.

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% and the single enum parameter already documents its allowed values and default (30d). The description's 'Day by day' phrasing is consistent with period scoping but adds no syntax, format, or interpretation guidance beyond the schema.

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 enumerates the metrics returned (total and paid subscribers, followers, views) at day granularity, which gives a reasonable sense of the resource. However it is a noun fragment with no verb and makes no attempt to distinguish itself from close siblings like get_publication_stats, get_audience_insights, or get_post_stats, so an agent must infer the difference.

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?

There is no statement of when to use this tool versus the many adjacent stats/insights siblings, and no mention of prerequisites or exclusions. The only routing hint is implicit in the word 'daily', leaving the agent to guess between several overlapping analytics tools.

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