sonarr_bulk_delete_blocklist

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

Annotations already declare destructiveHint=true, and the description repeats 'DESTRUCTIVE: this deletes data' without adding new context like permanence, affected entries, or confirmation requirements. It adds no behavioral insight beyond 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 with no wasted words, but the second sentence merely echoes the destructive annotation, and 'blocklist bulk' is awkwardly phrased. It's concise but under-specified.

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 destructive bulk operation with an opaque body parameter, the description is severely incomplete. It lacks any explanation of what the body must include, what 'bulk' means in practice, or how it relates to sonarr_delete_blocklist. The output schema exists but doesn't compensate for the missing operational guidance.

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 has a single 'body' parameter with no description and 0% coverage. The description doesn't mention this parameter or explain what the bulk deletion request body should contain, leaving the agent to guess the required payload.

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?

'Delete blocklist bulk' clearly identifies the verb (delete) and resource (blocklist), and 'bulk' distinguishes it from the sibling sonarr_delete_blocklist for single entries. However, it doesn't explicitly contrast with related tools like sonarr_list_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 guidance is provided on when to use this tool versus alternatives. The sibling sonarr_delete_blocklist exists for individual deletions, but the description doesn't mention that distinction or any prerequisites for bulk deletion.

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