radarr_list_release

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

Annotations already declare readOnlyHint=true, so the safe read-only nature is covered. The description adds no behavioral context beyond restating the action and parameter name; it does not disclose pagination, output structure, or whether a prior search is required.

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 compact with only two sentences, quickly conveying the purpose. While the second sentence is redundant with the schema, it is not verbose or disorganized, earning a high conciseness score.

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 the tool's simple nature and the presence of an output schema, the description could be sufficient, but it lacks crucial context about when to use it and what the results represent. The absence of any comparison to sibling tools like radarr_search_releases makes it incomplete for an agent.

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%, and the description only mentions 'Query params: movie_id' without explaining what movie_id represents or how it affects the results. The parameter's purpose is entirely undocumented, relying solely on the name.

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 action 'List release search results' with a specific resource and verb. It distinguishes itself from sibling tools like radarr_list_releaseprofile by focusing on release search results, though it does not explicitly differentiate from radarr_search_releases.

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 like radarr_search_releases or radarr_push_release. It does not mention any prerequisites or context in which listing release results is appropriate.

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