seerr_get_discover_tv_genre

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

Annotations provide readOnlyHint=true, and the description describes a read operation, so there is no contradiction. However, the description adds no extra behavioral context such as pagination, authentication requirements, or return format; it merely restates the basic function.

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, concise sentence with no filler or redundancy. It is front-loaded and gets straight to the point, though it is so terse that it sacrifices useful detail.

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?

With three parameters (one required), an output schema, and annotations, the description is inadequate. It fails to explain the required genre_id, the role of page and language, or any pagination behavior, leaving the agent without enough information to invoke the tool correctly.

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 explain any of the parameters (genre_id, page, language). 'By genre' vaguely relates to genre_id but does not specify valid values, format, or the purpose of the other parameters.

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 action (Discover) and the resource (TV shows) with a genre filter, which aligns with the tool name and distinguishes it from movie-genre or network/language discovery variants. However, it largely restates the name without adding extra nuance, so it doesn't fully excel.

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 gives no guidance on when to use this tool versus siblings like seerr_get_discover_movies_genre or seerr_list_discover_tv. The only implied usage is the genre focus, but there is no explicit context or exclusions.

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