sonarr_get_blocklist

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

No annotations are provided, so the description carries the burden. It adds useful domain context by explaining that blocklisted releases won't be re-grabbed. However, it does not explicitly state that this is a read-only operation (though 'Get' implies it) or describe pagination behavior beyond what the schema already provides.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose and the meaning of the blocklist. Every word earns its place with no redundancy or filler.

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 paginated list retrieval tool, the description is nearly complete. It explains the domain concept (blocklist), and the schema covers pagination parameters. It could optionally mention the return type, but the tool name and description make it clear it returns a list, so it is sufficient.

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 100% for both parameters (page, pageSize), and the description adds no additional parameter meaning. The baseline of 3 is appropriate since the schema fully documents the parameters.

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 the specific verb 'Get' with the resource 'Sonarr blocklist' and clarifies what the blocklist contains (blocked/failed releases that won't be re-grabbed). This clearly distinguishes it from sibling tools like sonarr_delete_from_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?

The description provides clear context that this is the retrieval operation for the blocklist, which implies when to use it (when you want to view blocked/failed releases). It doesn't explicitly name alternatives or exclusions, but the verb 'Get' naturally contrasts with delete/modify siblings, making the usage context clear.

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