list_blocklist_movie

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

Annotations already declare the operation as read-only, idempotent, and non-destructive, so the description does not need to restate that. It adds the HTTP GET endpoint, but no additional behavioral context such as pagination, authorization requirements, or result filtering semantics.

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 very short and front-loaded: it states the action, the endpoint, and the argument in a compact structured format. It has no filler, though the brevity comes at the cost of missing behavioral and usage detail.

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 output schema and annotations cover return values and safety, and the tool has only one optional parameter. Still, the description lacks enough context about when to use this vs. list_blocklist and what movie_id actually filters, leaving some ambiguity 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?

The schema already shows movie_id as an optional integer with a null default. The description only restates it as a query parameter without explaining what it does or how it affects the returned blocklist. With 0% schema description coverage, this is insufficient.

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 the operation as 'Read' and provides the endpoint GET /api/v3/blocklist/movie, making the target resource reasonably clear. However, the prose only says 'Read Blocklist' and does not explicitly distinguish this from the sibling list_blocklist tool.

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?

There is no guidance about when to use this tool instead of list_blocklist or any other alternative. It also does not explain whether movie_id is required for filtering, optional, or what happens when it is omitted.

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