Series seasons and episodes

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: a movie ref produces an error rather than an empty result, the default season is the latest, and streaming links are deliberately omitted from the output.

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 tight paragraphs with the purpose front-loaded and the operational caveats second. Minor duplication of the 'default season is the latest' fact already present in the season schema description keeps it from being fully waste-free.

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?

With no output schema, the description does the necessary work of naming the returned fields and flagging that streaming links are absent. Pagination semantics for limit (e.g., whether more episodes exist beyond the cap) are the one notable remaining gap.

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 description coverage is 100%, so ref, limit and season are already fully documented, including that the season default is the latest. The description's only added meaning is the series-vs-movie ref constraint, which is a useful but small increment over the schema's pattern and 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?

States a specific verb and resource ('List the seasons of a series and the episodes of one season') and even enumerates the returned fields (title, summary, length, publish date). It is clearly distinguishable from vod_search and vod_title, which are named as the upstream discovery tools.

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?

Gives explicit triggers ('when the user wants episodes, how many seasons exist or the newest episode') and explicit sequencing ('Use after vod_search or vod_title'), plus a when-not condition: a movie ref returns an error. This is close to complete routing guidance.

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