Get daily stats

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds useful data semantics beyond that. It explains one-row-per-day output, what each row represents, null handling for missing days, and the start date for young publications.

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?

The description is front-loaded with the core purpose and remains efficient. The second sentence repeats the metric list somewhat, but overall it is appropriately sized and easy to scan.

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-parameter read-only stats tool with no output schema, the description gives enough return-shape context: row granularity, included metrics, null behavior, and publication start handling. It could be stronger only by clarifying how it relates to sibling stats tools.

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?

The only parameter, period, is fully documented in the schema with an enum and default. The description references the period but adds no extra meaning beyond the schema, so the baseline of 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 clearly states a specific resource and granularity: daily rows containing total subscribers, paid subscribers, followers, and views. It is understandable without opening the schema, but it does not explicitly distinguish this tool from neighboring stats tools such as get_publication_stats or get_audience_insights.

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?

The usage is implied by the description: use it for day-by-day audience metrics matching the dashboard home and Audience charts. However, it does not say when to choose this over sibling stats tools or when not to use it.

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