seerr_list_discover_trending

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

The annotation readOnlyHint=true already indicates a safe read operation, but the description adds no behavioral context beyond the name. It does not disclose defaults (e.g., time_window='day', media_type='all'), pagination behavior, or what happens with invalid 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 extremely short and front-loaded, but it is a fragment rather than a complete, informative statement. Under-specification is not conciseness; the phrase could be expanded to a full sentence while still being 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?

Although an output schema exists, the description does not explain the tool's overall purpose, the meaning of 'trending', or how the four parameters affect results. This leaves a significant gap for a tool with no parameter descriptions and no guidance.

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 does not compensate. It does not explain the meaning or accepted values for page, language, media_type, or time_window, leaving the agent to infer from parameter names alone.

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 'Trending movies and TV' identifies the resource but lacks a verb such as 'list' or 'get', making it a noun phrase rather than a clear action statement. It does not distinguish itself from sibling tools like seerr_list_discover_movies or seerr_list_discover_tv, leaving ambiguity about whether it returns a combined list or something else.

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 usage context is provided. The description gives no indication of when to use this tool versus alternatives like seerr_list_discover_movies or seerr_list_discover_tv, nor any mention of parameters that control scope (e.g., media_type or time_window).

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