seerr_get_discover_keyword_movies

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

The description says 'Get', which is consistent with readOnlyHint=true, so no contradiction. It adds no extra behavioral context beyond the annotation, such as pagination or response shape, but the annotation already signals a safe read operation, so the bar is lower.

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 short sentence with no filler or redundant information. It is front-loaded and efficient, though minimal, fitting the simple nature of the tool.

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?

The tool is a simple read operation with an output schema and defaulted parameters, so a short description is partly acceptable. However, the absence of usage guidance and parameter semantics leaves gaps for an agent distinguishing this from similar discover tools, making it minimally viable but not fully complete.

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 three parameters. While names like keyword_id, page, and language are somewhat self-explanatory, the description does not clarify the required keyword_id or how page/language influence results, leaving the agent to rely solely on schema field names.

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 uses a specific verb 'Get' and identifies the resource as 'movies' filtered by keyword, distinguishing it from siblings like seerr_get_keyword (keyword details) or seerr_list_discover_movies (all movies). However, 'from keyword' is slightly ambiguous because it doesn't explicitly reference the required keyword_id parameter, though the schema clarifies that.

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 offers no guidance on when to use this tool versus alternatives like seerr_list_search_keyword or seerr_get_keyword. It does not mention prerequisites (e.g., obtaining a keyword ID from a search) or scenarios where this tool is preferred over others.

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