Get a user's anime or manga list

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

Beyond readOnlyHint/openWorldHint, the description discloses pagination semantics (chunk counts across all statuses combined), the need to check hasNextChunk, and AniList's ~11,000 entry cap for older entries. This is valuable behavioral context not present in annotations.

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 front-loads the core purpose in the first sentence, then covers usage and pagination in clearly separated clauses. Every sentence adds operational value—no filler.

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 paginated external-API tool, the description covers grouping, pagination loop (hasNextChunk/increment chunk), API cap, and username-handling. With an output schema present, there is no missing return-value information; the description is fully self-sufficient for invocation decisions.

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?

Although schema descriptions cover all four parameters 100%, the tool description enriches 'chunk' and 'perChunk' by explaining they are AniList's own pagination mechanism and that counts are across ALL statuses combined. It also clarifies the 'user' parameter accepts an exact username directly, which is not obvious from the schema alone.

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?

Description opens with a specific verb and resource: 'Get a user's AniList anime or manga list, grouped by status/custom list', enumerating returned fields (status, score, progress, dates). It also clarifies it works for any public/unlisted user, distinguishing it from user-profile tools like get_user_profile or get_full_user_info.

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?

Explicitly tells agents when not to call search_user: 'Accepts an exact AniList username directly — no need to call search_user first unless you only have a partial/fuzzy name.' Also frames pagination usage with chunk/perChunk and hasNextChunk, giving clear operational context.

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