sonarr_delete_blocklist

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

The description repeats 'DESTRUCTIVE: this deletes data' which directly mirrors the annotations (destructiveHint=true, readOnlyHint=false). It adds no new behavioral context such as irreversibility, permissions, or side effects beyond what annotations already state.

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 two short sentences, directly front-loaded with the purpose. No wasted words or redundant detail beyond the necessary destructive warning.

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 is simple, but with a single undocumented id parameter and no mention of behavior on success, failure, or related constraints, the description is minimal. The output schema exists but does not help the agent understand input semantics.

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 sole parameter 'id' has no description in the schema (0% coverage), and the tool description does not clarify what id represents (e.g., blocklist entry ID). The description fails to compensate for the missing parameter information.

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 ('Delete blocklisted releases') with a specific verb and resource. It distinguishes from the sibling sonarr_bulk_delete_blocklist by implying a single-item deletion, and the destructive warning adds clarity.

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 guidance on when to use this tool versus alternatives like bulk delete or list. The destructive warning is a caution, not usage direction, and there is no mention of conditions or exclusions.

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