tmdb_trending

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing beyond a basic fetch: no rate limits, no note that results are a ranked list, no default behavior when time_window is omitted.

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?

One short, front-loaded sentence with zero waste. It is efficient but under-specified for the routing ambiguity it leaves unresolved.

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?

No output schema, three parameters, none required — yet the description never says what is returned (ranked list? paginated?), what the default media_type/time_window is, or how results differ from tmdb_popular_tv. Too thin for a tool sitting in a dense cluster of TMDB siblings.

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 coverage is 67% and the two documented enums just restate allowed values ('movie, tv, or all', 'day or week'). The description mentions only movies/TV, silently omitting the 'all' option, and says nothing about defaults (which time_window applies if omitted) or api_key handling.

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?

States a specific verb and resource (get trending movies/TV on TMDB), so the agent knows the operation. But it never distinguishes itself from sibling trending/popular tools like tmdb_popular_tv, tmdb_now_playing, tmdb_upcoming, or tmdb_search_movies/tmdb_search_tv.

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 indication of when to choose this over the many nearby TMDB siblings (popular, now_playing, upcoming, search). The only implied usage is 'trending', which the name already carries.

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