Get AniList site statistics

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

Annotations already indicate read-only and open-world hints, and the description adds practical behavior details: default to last 7 days, newest-first ordering, and the AniList-side perPage cap that nullifies any concern about the tool's own limit. These go beyond the structured hints.

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?

Three sentences, front-loaded with the core function, followed by usage guidance and a useful quirk. Every sentence adds distinct value with no fluff.

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?

The tool is simple with an output schema already present, and the description fully covers purpose, use cases, defaults, and a behavioral quirk. Nothing important is missing for an agent to select and invoke it correctly.

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%, providing baseline 3. The description adds value by explaining that defaults correspond to a 7-day window and that page/perPage are used to 'go further back', linking them to time range rather than just pagination mechanics.

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 the tool gets AniList's site-wide statistics (new users/anime/manga daily counts) in newest-first order. It distinguishes itself from siblings by explicitly noting this is not for anime data, unlike get_media_statistics or get_user_stats.

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 description explicitly says when to use it ('useful for questions about AniList's growth/activity') and when not to ('not for anime data'). It also explains how to access historical data via pagination, providing clear usage context.

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