seerr_get_discover_movies_genre

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

The annotation readOnlyHint: true already indicates a safe read operation, and the description ('Discover movies by genre') does not contradict this. However, the description adds no extra behavioral context beyond the annotation, such as pagination behavior or required filters, but given the annotation coverage, this is adequate.

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 (one sentence), but it is under-specified rather than appropriately concise. It omits essential information about parameters and usage, making it more of a placeholder than a useful tool description.

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?

Given the presence of an output schema and readOnly annotation, the description is for a simple discovery endpoint. However, it fails to mention required parameters (genre_id) or the optional language/page parameters, and it provides no context about the response structure (though output schema exists). The description is minimal and leaves several gaps for correct invocation.

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 only hints at genre_id via 'by genre'. It does not explain the page parameter (pagination) or the language parameter (default null), leaving the agent without meaningful semantics for two of three parameters. The description fails to compensate for the lack of schema documentation.

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 identifies the action ('Discover movies') and the specific filter ('by genre'), which maps directly to the resource and scope. It is sufficiently specific to differentiate from sibling tools like seerr_get_discover_movies_language or seerr_get_discover_movies_studio by name, though the description itself does not explicitly mention alternatives.

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 provides no guidance on when to use this tool versus the many sibling discovery tools (e.g., seerr_get_discover_movies_language, seerr_list_discover_movies_upcoming). There is no mention of context, prerequisites, or exclusions, leaving the agent to guess.

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