Get anime episodes

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds behavioral context: paginated (~100 per page), and the returned fields (titles, air dates, filler/recap flags). This goes beyond what annotations provide, though it could mention sorting or potential limits.

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, front-loaded with the core purpose, then pagination note, then source of ID. Every sentence adds value without redundancy.

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, schema coverage, and annotations, the description is complete. It covers the input (mal_id), behavior (paginated list), output fields (titles, dates, flags), and prerequisite (use search_anime). No output schema needed.

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 baseline is 3. The description adds meaning by linking the id parameter to mal_id and explaining page usage for pagination. It does not duplicate the schema but clarifies how the parameters are used.

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 uses a clear verb 'List' and specifies the resource 'anime's episodes', including the key identifier 'by mal_id' and the returned data (titles, air dates, filler/recap flags). This distinguishes it well from sibling tools like get_anime (which returns anime details) and search_anime (which searches for anime).

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 the user to get the mal_id from search_anime and explains pagination with the page parameter for long series. It provides clear context but does not explicitly mention when not to use this tool or list alternatives for episode filtering.

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