List an anime's characters with name, native name, role, image, and favourites from public AniList data, paginated.
List an anime's characters. Returns an anime's cast (character name, native name, billed role, image, favourites), paginated. Credential-free public AniList data.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | AniList anime id | |
| page | No | 1-based page number, default 1 | |
| per_page | No | Results per page, default 10, max 50 |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the output fields and pagination behavior, which is basic. It does not mention rate limits, authentication needs, or any side effects. However, for a simple read-only API, this is adequate.
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 purpose and core output. Every sentence adds value: the first specifies action and result, the second clarifies it's public and free. No redundancy or 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?
Given the tool's simplicity (3 parameters, no output schema, no nested objects), the description is complete. It states the return type (cast with specific fields) and pagination. There is no missing information for an agent to use this tool effectively.
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 has 100% description coverage for its three parameters. The description adds no additional meaning beyond what the schema already provides (id, page, per_page defaults and limits). Baseline score of 3 applies as the schema does the heavy lifting.
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 lists an anime's characters with specific output fields (character name, native name, billed role, image, favourites) and pagination. It distinguishes from sibling tools like anime_character (single character) or anime_character_search (search across characters) by making 'anime's characters' the focus.
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 implicitly tells when to use it (when you need characters for a specific anime) but does not explicitly mention when not to use it or recommend alternatives like anime_character or anime_character_search. The 'Credential-free public AniList data' line hints that no auth is required but stops short of full guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.