Discover TMDB Movies

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

With no annotations, the description must disclose behavior. It only mentions filtering capabilities but does not explain pagination, default sorting, genre mode matching, or that watch provider filters require region. It also does not state that this is a read-only operation or what results look like.

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 filler. It efficiently lists the main filter dimensions, although it is too brief for a tool with this many parameters.

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 tool with 22 parameters, no annotations, and no output schema, this description is severely under-specified. It omits all usage context, return format, and critical behavioral constraints like the default sort or how to combine filters.

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 only gives broad categories (e.g., 'date' could map to releaseDateFrom/To or releaseYear). It does not explain any of the 22 parameters, including nuanced ones like genreMode, keywordMode, castIds vs personIds, or watchProviderIds.

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 the verb 'Discovers' with the resource 'movies' and lists key filter dimensions (genre, date, rating, runtime, language, provider, sort). This clearly indicates a filtered movie listing tool, though it does not explicitly distinguish it from tmdb_search_movies or tmdb_list_movies.

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 guidance on when to use discover vs search or list. There are no references to alternatives or exclusions. The description gives no context about prerequisites or typical use cases.

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