Get up next

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that about ordering, what an item in the result looks like, or pagination interaction with the view modes, so it meets only the lowered bar set by 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?

A single dense sentence, front-loaded with the resource and immediately followed by the mode semantics. Every clause carries information; nothing is redundant with the schema or title.

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 5-parameter read tool with no output schema, the description covers mode selection but says nothing about what the returned items are (episode vs show objects) or their ordering. It is adequate to invoke the tool but leaves the agent guessing about the result shape.

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?

The schema documents days, limit, offset and hide_unreleased, but the critical 'view' enum has no description in the schema — the description supplies the meaning of all four enum values, which is a real addition beyond structured data. It does this compactly and completely, though it does not clarify how days and hide_unreleased interact across the non-matching views (it leaves that to the schema).

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 concrete verb+resource ('Get next episodes') and enumerates all four view modes with a short gloss for each, so an agent knows exactly what data this returns. It doesn't distinguish itself from the sibling get_watchlist, even though the 'watchlist' view clearly overlaps with it.

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 parenthetical glosses implicitly tell the agent which view to pick for a given situation (in-progress vs caught-up vs all followed vs watchlisted), which is useful routing guidance. However, there is no explicit statement of when to prefer this tool over siblings like get_watchlist or get_sync, and no exclusions.

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