Get an anime/manga's score/status distribution

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavioral context by specifying the data is 'across all AniList users' and that it returns a histogram, going beyond just saying 'get stats.'

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 two sentences long, front-loaded with the core function, and the second sentence adds a practical usage tip. No fluff or repetition.

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?

Given the simple two-parameter schema, an output schema, and annotations, the description fully covers what the tool does and when to invoke it. The output schema removes the need to explain return values, and the description plus annotations provide sufficient context.

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 schema provides 100% description coverage for both parameters (id and type), so the description does not need to add much. The hint to use search_media adds a connection between tools but does not deepen parameter understanding beyond what the schema already offers.

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 what the tool does: it retrieves watch/read-status counts and score distribution histograms for an anime/manga across all AniList users. This specific verb and resource distinguish it from sibling tools like get_media or get_media_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 advises to use search_media first to resolve a title to an AniList ID, which is a clear usage prerequisite. It does not mention when not to use this tool or name alternatives, but the context is sufficient for selecting it.

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