seerr_list_genres_movie

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

The readOnlyHint annotation is consistent with the description's 'Get list' wording. The description adds 'official TMDB' as a source detail, but does not disclose other behavioral aspects like language handling, response shape, or any filtering limitations. Since annotations already cover the read-only nature, this is adequate but not rich.

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. Every word adds meaning, and it is appropriately concise for a simple list operation.

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 simple read-only list tool with an output schema and annotation, the description is minimally viable. However, it omits guidance on the language parameter and alternative tools, so it is not fully complete. The output schema covers return values, but parameter semantics and usage context have gaps.

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 input schema has one optional 'language' parameter with no description and schema_description_coverage is 0%. The description does not mention language at all. The parameter name is somewhat self-explanatory, but the agent receives no information about expected format, allowed values, or effect.

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 'Get list of official TMDB movie genres' uses a specific verb ('get list') and a clear resource ('official TMDB movie genres'). It distinguishes from sibling tools like seerr_list_genres_tv and seerr_get_discover_movies_genre by explicitly targeting movie genres.

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 versus alternatives, such as seerr_list_genres_tv or seerr_get_discover_movies_genre. The description does not mention exclusions, prerequisites, or context beyond the obvious 'use for movie genres'.

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