get_title_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 useful behavior: episodes are paginated by limit and continue via the previous page's next_cursor, and omitted season returns all in order. It stops short of noting ordering guarantees beyond 'in order' or error behavior for invalid seasons.

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?

One front-loaded purpose sentence followed by a tight Args block; every line adds information. Slightly mechanical format but no wasted prose.

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 an output schema present, return values need not be described, and pagination plus filtering is fully specified. Enough to call correctly; only edge-case behavior (invalid season, cursor expiry) is unaddressed.

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 0%, so the description carries the full burden — and it does: id is identified as the series title id, season as an optional single-season filter, limit as page size, and cursor as the prior page's next_cursor. Only minor gaps (e.g. limit bounds/default of 50) remain.

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?

Specific verb ('List') plus resource ('a series' seasons and episodes with their ratings'), which clearly separates it from siblings like get_title_credits or get_title_reviews. It doesn't explicitly name the sibling it replaces (e.g. get_title for the overview), so it falls short of a 5.

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 args notes imply usage ('Omit for all, in order') and explain the paging flow via cursor. There is no explicit statement of when to choose this over get_title or other title-detail siblings, so routing guidance is only implied.

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