List TMDB TV Series

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'lists' without mentioning pagination, language parameters, response format, or any side effects. This is insufficient for an agent to understand the full behavior of the tool.

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 concise sentence that front-loads the verb and resource. It contains no filler or redundant information, earning a top score for conciseness.

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?

The tool is simple, but with no output schema and no annotations, the description should provide more context. It omits usage guidance, parameter details, and behavioral notes, leaving the agent under-informed about pagination and language handling.

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%, so the description must compensate. It mentions the category values, but these are already present in the schema's enum. It does not explain the 'page' or 'language' parameters, leaving them undocumented even though they affect the result.

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 clearly states the action (lists) and the resource (TV series), and specifies the exact categories (airing-today, on-the-air, popular, top-rated). This is specific enough to distinguish from sibling tools like tmdb_search_tv or tmdb_get_tv_series.

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 implies the tool is used when you need a curated list of TV series by category, but it provides no explicit guidance on when to prefer it over alternatives like tmdb_trending_tv or tmdb_discover_tv. It lacks any exclusion criteria or alternative recommendations.

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