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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds the useful context that this is credential-free public AniList data, which is not in the annotations. It also discloses pagination behavior and result clamping. It does not discuss rate limits or potential data freshness constraints, so 4 rather than 5.

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 front-loaded with the core purpose, then presents parameters compactly, and ends with a routing pointer to anime_title. No redundant or filler sentences.

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 2-parameter, read-only, public paginated list, the description covers return fields, ordering, data source, pagination limits, and cross-references a sibling. An output schema is present, so return shape details are not needed. The only minor gap is lack of guidance on when this tool is not the right choice.

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 schema already documents both parameters completely. The description repeats the same definitions ('page: 1-based page number, default 1', 'per_page: Results per page, default 20, clamped to 50') without adding new semantic information. Baseline 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?

States a specific verb and resource ('Returns upcoming anime episode broadcasts'), enumerates the returned fields (episode number, air time, countdown, normalized title), and specifies ordering ('soonest first'). This distinguishes it from siblings like anime_search or anime_title.

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 states 'Use anime_title to get an anime,' routing the agent to the right sibling for title lookup. However, it does not explain when to prefer this schedule over other anime siblings (e.g., anime_rankings, anime_title_recommendations) or when the tool is not appropriate.

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