radarr_list_blocklist_movie

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

The readOnlyHint annotation already indicates a safe read operation, and the description adds no behavioral context beyond that. It does not mention filtering behavior, return format, pagination, or any constraints, leaving the tool's behavior largely undisclosed.

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 only two sentences and is short, but the second sentence merely restates the parameter name without adding value. While concise, it lacks structured, useful information; it is under-specified rather than efficiently specified.

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 and a readOnly annotation, the description is insufficient for this tool. It does not clarify that this is blocklist-specific, how movie_id filters results, or how the output relates to other list tools, leaving significant gaps in context.

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 schema lists movie_id with no description, and the description only repeats 'Query params: movie_id' without explaining the meaning, format, or effect of the parameter. With 0% schema description coverage, the description completely fails to compensate for the missing parameter semantics.

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 says 'List movies' which identifies a generic action and resource but fails to mention 'blocklist' that is central to the tool's name. It does not distinguish this from sibling tools like radarr_list_movie or radarr_list_blocklist, making the purpose ambiguous.

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 about when to use this tool versus alternatives. The description does not explain that this lists movies in the blocklist or how it differs from other list endpoints, so the agent cannot choose it appropriately.

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