radarr_list_movie

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

The readOnlyHint annotation already declares this as a safe read operation, and the description's 'List movies' is consistent. However, the description adds no extra behavioral context such as pagination, response structure, or the effect of filters. It does not contradict annotations, but also does not go beyond them.

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 very brief and to the point, with no wasted words. It is appropriately sized for a simple list operation, though the brevity contributes to missing parameter details.

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 that an output schema exists and the tool belongs to a large family of list/get tools, the description is incomplete. It lacks usage guidance, omits one parameter, and does not explain how the query params affect results, making it insufficient for an agent to select and invoke confidently.

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 description lists only tmdb_id and language_id, omitting exclude_local_covers entirely. It provides no explanation of what these parameters do beyond their names, leaving the schema's names and defaults to carry all meaning. With 0% schema description coverage, this is insufficient.

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 tool lists movies, which is a specific verb+resource. It distinguishes from siblings like radarr_get_movie by using 'list' rather than 'get', but does not explicitly call out the difference.

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 radarr_get_movie for a single movie or radarr_list_moviefile for movie files. The description merely states the function and query params without any contextual usage advice.

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