Get an anime/manga's production staff

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

With readOnlyHint and openWorldHint annotations covering the read-only nature, the description adds a non-obvious behavior: 'No explicit ordering is requested — don't assume results are sorted by role or popularity (unlike get_staff ... which IS popularity-sorted).' This adds useful caveat beyond the 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?

Two sentences with no filler: the first states the action and scope, the second provides workflow and ordering caveat. Information is front-loaded and economical.

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?

The description covers the core purpose, prerequisite workflow (search_media), and a key behavioral caveat (unsorted results). The output schema exists, and annotations cover safety and open-world nature, so no critical context is missing.

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% with clear descriptions for all four parameters (id, type, page, perPage). The description only ties `id` to the search_media workflow but adds no parameter-specific syntax or constraints beyond the schema, so the baseline of 3 applies.

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 'List an anime/manga's staff (director, writer, character designer, author, illustrator, etc.) with their role.' This is a specific verb+resource+scope that clearly distinguishes from sibling tools, especially by noting 'unlike get_staff's reverse-direction lookup'.

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?

Explicit workflow guidance is provided: 'Use search_media first to resolve a title to its AniList ID.' It also contrasts with get_staff, telling the agent when not to use this tool, making the usage context unambiguous.

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