Get an anime/manga's characters

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

Even with readOnlyHint=true in annotations, the description adds valuable behavioral context: results are not guaranteed to be grouped by role or sorted by popularity, with a live example that Main-role characters can appear later than Supporting ones. This discloses non-obvious behavior beyond schema/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?

Three sentences, front-loaded with the core purpose, then workflow, then the key ordering caveat. Every sentence earns its place; no filler 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?

With an output schema present, the description sufficiently covers what is returned (characters, roles, voice actors), how to prepare the ID, and the critical ordering uncertainty. The agent has enough context to invoke and interpret results 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%, so the baseline is 3. The description adds extra meaning for the 'id' parameter by telling users to resolve titles via search_media, and clarifies type-specific output (voice actors only for anime), which goes beyond the bare schema descriptions.

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 states a specific action and resource: 'List an anime/manga's characters' with role and voice actors. This clearly distinguishes it from sibling tools like get_character (reverse lookup) and search_media (title resolution).

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?

It explicitly instructs the agent to 'Use search_media first to resolve a title to its AniList ID', establishing a clear workflow. It also contrasts with get_character/get_staff's reverse-direction lookup, helping the agent know when this tool is the right choice.

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