Get the anime airing schedule

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the 'confirmed live' nature, the soonest-airing ordering, and the notYetAired parameter's behavior of swapping to past-only results. It also reveals that manga IDs are rejected with the same not-found error as nonexistent IDs, preventing agent confusion.

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 deliver the core purpose, usage modes, and edge-case behavior with no filler. The structure front-loads the main function and logically nests the optional mediaId usage and the manga-related error note.

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 complexity (4 parameters, output schema present, annotations present), the description covers all necessary operational aspects: scheduling modes, ordering, live status, manga exclusion, and error semantics. With a rich output schema available, it is complete without needing to restate return formats.

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?

Although the schema has 100% parameter coverage, the description adds essential semantic guidance: omitting mediaId yields the site-wide schedule, while passing it gives a single title's next air time. It also explains the effect of notYetAired and the manga ID error nuance, which are not fully covered by the 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 the tool returns anime episode air times, sorted by soonest-airing first, and distinguishes site-wide vs specific-title modes. This clearly separates it from sibling tools like get_media or search_media, which return different types of media information.

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 instructs when to omit mediaId (site-wide schedule) vs when to pass it (specific title), and tells the user to obtain the ID from search_media/get_media. It also states the anime-only restriction and the resulting not-found error for manga IDs, giving clear usage boundaries and expectations.

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