sonarr_list_blocklist

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

The annotation readOnlyHint=true covers the safety profile. The description adds no behavioral context beyond the action itself, such as pagination behavior, filtering implications, or whether all blocklist entries are returned. It does not contradict the annotation.

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 extremely short, but the second sentence 'Query params: sort_key, sort_direction' merely repeats schema information, adding no value. The entire description is under-specified, but there is no waste beyond that redundancy.

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?

The tool has 6 optional parameters and an output schema. The description does not explain the purpose of the filtering parameters (protocols, series_ids) or pagination controls, leaving the agent to infer from parameter names. This is insufficient for correct usage.

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 needed to compensate. It only mentions sort_key and sort_direction, ignoring page, page_size, protocols, and series_ids, which are present in the schema. Even for the mentioned params, no additional meaning is provided beyond their names.

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 uses a specific verb 'List' and a specific resource 'blocklisted releases', clearly identifying the tool's function. It is distinct from sibling delete operations like sonarr_delete_blocklist.

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 usage guidance is provided. The description does not explain when to use this tool, what assumptions to make, or when to prefer an alternative. The parameter mention is not a usage guideline.

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