Search TMDB TV Series

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

With no annotations, the description carries the burden for behavioral disclosure. It adds useful detail about searching original, translated, and alternative names, but does not disclose behavior related to pagination, language handling, or response structure. This is limited but not misleading.

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?

A single, front-loaded sentence: 'Searches TV series by original, translated, and alternative names.' Every word is useful, with no redundancy or filler.

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 has 5 parameters, no output schema, and no annotation coverage. The description only addresses the query concept and resource type, omitting optional parameters, return format, and any caveats. For a search tool of this complexity, the description is under-specified.

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 clarifies that the query parameter searches by original, translated, and alternative names, which adds meaning beyond the schema's bare type definition. However, it does not describe page, language, firstAirYear, or includeAdult parameters, leaving significant gaps.

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?

Clearly states it searches TV series by original, translated, and alternative names, specifying both the resource (TV series) and the scope (name fields). This distinguishes it from sibling search tools like tmdb_search_movies and tmdb_search_multi.

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 this tool is for searching TV series by name, but it does not explicitly state when to use it over alternatives like tmdb_search_multi, nor does it mention exclusions or prerequisite conditions. Usage context is implicit rather than explicit.

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