get_blocklist

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully explains why releases appear in the blocklist, but it does not disclose response format, pagination behavior, or explicitly confirm read-only semantics beyond the verb 'List'. No contradiction exists.

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?

Two tight sentences with no filler. The first sentence delivers the core purpose and expected content; the second adds just enough domain context to explain the list's provenance.

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 read-only list endpoint with all-optional parameters and a well-described schema, the description plus schema gives an agent enough to invoke it correctly. A minor gap is not naming the companion removal tool or detailing the output shape, but the description partially covers output content already.

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 high (80%), so the schema already documents page, sort_key, movie_ids, and page_size, while sort_direction's allowed values are given as an enum. The description adds no parameter-specific guidance, which is acceptable but not additive.

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?

Description opens with a specific verb ('List') and a distinct resource ('blocklisted releases'), then enumerates the key data attributes ('what was blocked, when, from which indexer and why'). This makes the tool's function unmistakable and distinguishes it from related listing tools like get_history or get_queue.

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 for when entries belong here: after a failed download or an explicit blocklist. This tells an agent when this tool is relevant, though it does not explicitly name alternatives or list when-not-to-use conditions.

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