radarr_list_moviefile

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

The readOnlyHint annotation already indicates a safe read operation, so the description adds no additional behavioral context. It merely restates the query parameters without disclosing results behavior such as pagination, default list size, or how multiple filter values are combined.

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 appropriately short and front-loaded with the core action. The second sentence about query params is concise but adds marginal value since the parameters are already visible in the schema. It is efficient, though a phrase like 'optionally filtered by' would improve clarity.

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 list operation with a readOnlyHint and output schema, the description is nearly adequate. However, the lack of parameter semantics and usage guidance leaves some gaps, particularly for an agent deciding whether to use movie_id, movie_file_ids, or both. It is not severely incomplete but is not fully self-contained.

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 only lists parameter names ('movie_id', 'movie_file_ids') without explaining their meanings or usage. Given that the schema has 0% description coverage, the description fails to compensate by clarifying what these IDs refer to or how they filter the results.

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 'List movie files' clearly states the action (list) and the resource (movie files), distinguishing it from sibling tools like 'radarr_get_moviefile' which retrieves a single file. The verb and resource are specific, leaving no ambiguity about the tool's purpose.

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 alternatives such as radarr_get_moviefile or how the query parameters (movie_id, movie_file_ids) should be applied. It lacks any mention of whether these are optional filters or how they interact.

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