seerr_get_discover_movies_language

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

The annotation readOnlyHint=true already covers the read-only nature. However, the description adds no behavioral context such as pagination behavior, return format, or how the language filter is applied. It merely restates the purpose without disclosing any additional traits beyond the annotation.

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, compact sentence that is front-loaded with the core action and target. It is free of fluff and easy to read. The brevity is a strength here, though it sacrifices detail needed for other dimensions.

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?

Despite having an output schema (which removes the need to explain return values), the tool still has 3 parameters and ambiguous sibling relationships. The description does not provide enough context for an agent to know how to correctly set the parameters, especially the optional 'language_q'. The minimal text leaves significant gaps for a tool that appears to support filtered discovery.

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%, so the description must compensate. It only hints at the 'language' parameter through the phrase 'original language' but does not explain the meaning of 'page' or 'language_q', nor does it clarify language code format or the relationship between parameters. This is insufficient for a 3-parameter tool.

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 ('Discover') and resource ('movies') with a clear filtering scope ('by original language'). It is informative enough to convey the core function, though it does not differentiate itself from similar sibling tools like seerr_get_discover_tv_language or seerr_list_discover_movies.

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 explicit guidance on when to use this tool versus alternatives. With many sibling discovery tools, there is no mention of when to prefer this over seerr_get_discover_movies_studio or seerr_list_discover_movies. Usage is only vaguely implied by the literal phrase.

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