tmdb_trending

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

With no annotations, the description should disclose behavioral traits like API key requirement, rate limits, or response format. It only states the basic function, omitting that the 'api_key' parameter is needed for authentication and that it returns a list of trending items.

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 sentence with no unnecessary words. However, it is so brief that it borders on underspecification. It could benefit from adding key context while remaining concise.

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 presence of many sibling TMDB tools and no output schema, the description should at least mention that it returns a list of trending items or how to use the time_window. It fails to provide sufficient guidance for an agent to avoid confusion with similar tools.

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?

The schema already describes the enum types for media_type and time_window. The description only hints at media_type via 'movies or TV shows' but does not explain the 'api_key' parameter or add meaning beyond the schema. It compensates poorly for the 67% schema coverage.

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 retrieves trending movies or TV shows from TMDB, using a specific verb ('Get') and resource ('trending movies or TV shows'). It distinguishes from sibling tools like tmdb_search_movies (search) and tmdb_movie (single movie details) by focusing on trending content.

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 is provided on when to use this tool over other TMDB tools (e.g., tmdb_popular_tv, tmdb_search_movies). The description does not mention when not to use it or what scenarios are appropriate for trending vs. searching.

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