Get TMDB TV Season

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states what the tool gets, but does not disclose that it is a read-only operation, whether authentication is required, any rate limits, or what the response structure might be. There is no mention of required inputs or error conditions.

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 a single, front-loaded sentence with no redundant information. It efficiently states the core purpose and includes a key detail ('complete episode list'). It could be considered terse, but it is concise without being vague.

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 simple read-only tool, the description conveys the primary function and output sufficiently. However, given the lack of annotations and output schema, the description does not fully compensate for missing usage guidance, parameter semantics, or behavioral expectations. It is minimally acceptable but with clear gaps.

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 0%, and the description adds no information about the parameters (seriesId, seasonNumber, language) beyond what the schema already provides. It does not clarify semantics such as 0-based season numbering or the optional language format.

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 uses a specific verb ('Gets') and identifies the resource ('TV season') along with a distinctive scope ('complete episode list'). It clearly differentiates from sibling tools like tmdb_get_tv_episode (single episode) and tmdb_get_tv_series (series-level data).

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 description provides no guidance on when to use this tool versus alternatives. It does not mention that this tool is appropriate for fetching a full season with episodes, or that tmdb_get_tv_episode should be used for a single episode. No exclusions or contextual triggers are given.

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