radarr_list_blocklist

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

The readOnlyHint annotation already covers safety, so the description needs to add context beyond that. It lists query params (sort_key, sort_direction, movie_ids, protocols), which hints at filtering/sorting behavior, but it omits page and page_size, silently ignoring pagination. No side effects or rate limits are disclosed, and the annotation is not contradicted.

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 two sentences and very brief, which is efficient. However, the second sentence listing query params is incomplete (omits page/page_size) and adds only minimal value since those names already exist in the schema. It earns its place but could be tighter or more informative.

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?

Output schema exists so return values don't need description, and readOnlyHint covers safety. But for a list tool with six parameters, the description fails to mention pagination despite page/page_size appearing in the schema, and it doesn't explain the semantics of the listed query params. It is adequate for a low-complexity tool but has gaps.

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 for parameter meaning. It merely lists four of the six parameter names without explaining their format, allowed values, or how they affect results. For instance, 'sort_direction' could be asc/desc but is unstated. Only names are given, not semantics, leaving the agent to guess.

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 states a specific verb ('List') and resource ('blocklisted releases'), clearly distinguishing it from siblings like radarr_list_blocklist_movie and the delete/bulk-delete blocklist tools. It is not a tautology and leaves no doubt about the operation.

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 when-to-use guidance or alternatives are given. The description does not differentiate when to prefer this tool over radarr_list_blocklist_movie or other list tools, nor does it mention compatibility with delete operations. It simply names the tool and query params.

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