Get a user's statistics

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds value by noting that an exact username is accepted directly. However, it could clarify whether anime and manga statistics are always returned together or if there are cases where only one set is provided.

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 sentences with no waste. The purpose is front-loaded, and the key behavioral note about direct username acceptance is included without extraneous details.

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 single parameter, 100% schema coverage, annotations, and an output schema present, the description is complete. It covers what the tool does, how to supply the parameter, and when to avoid calling search_user.

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 input schema describes the 'user' parameter as 'AniList user ID, or username.' The description adds that it accepts an exact username directly and that prior lookup via search_user is unnecessary unless the name is partial or fuzzy. This enriches meaning 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 clearly states the tool returns anime/manga statistics including counts, mean score, time watched, episodes/chapters/volumes. It distinguishes from sibling tools like get_user_profile and search_user by specifying the exact resource and scope.

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 tells when to use this tool: when you need a user's stats. It provides guidance on not needing to call search_user unless you have a partial/fuzzy name, which differentiates it from the sibling search_user tool.

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