Discover TMDB TV Series

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says the tool 'discovers' TV series and mentions filter categories, but does not disclose return format, pagination, default sorting behavior, read-only nature, or any rate-limit or authentication considerations. This is insufficient for a tool with 19 parameters.

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 with no redundant words. It is front-loaded with the core action ('Discovers TV series') and lists key filters efficiently. Every word contributes to the meaning, making it appropriately sized for a high-level summary.

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?

Given the tool's high complexity (19 parameters, no annotations, no output schema), the description is far from complete. It omits crucial details such as pagination, default values, return shape, how filters combine (e.g., genreMode, keywordMode), and any constraints or edge cases. An agent would need substantial external knowledge to use this tool correctly.

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 attempts to compensate by listing filter categories. However, it only covers broad areas like genre, air date, rating, runtime, language, provider, and sort, leaving many parameters (page, region, genreMode, keywordMode, minVoteCount, firstAirDateFrom/To, excludeGenres, watchMonetizationTypes, etc.) unexplained or only vaguely implied. The mapping is incomplete and ambiguous, so the description adds limited semantic value beyond 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?

The description clearly states the tool discovers TV series and lists the filter dimensions (genre, air date, rating, runtime, language, provider, and sort), which conveys a specific verb and resource. It falls short of explicitly differentiating from similar siblings like tmdb_search_tv or tmdb_discover_movies, but the filter list suggests a distinct discovery-oriented purpose.

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?

No explicit guidance is given about when to use this tool versus alternatives such as tmdb_search_tv, tmdb_list_tv_series, or tmdb_trending_tv. The filter list implies it is for filtered discovery, but no when-to-use or when-not-to-use context is provided, leaving the agent to infer the appropriate scenario.

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