radarr_bulk_delete_blocklist

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

The annotation destructiveHint=true already communicates the destructive nature, and the description largely restates this with 'DESTRUCTIVE: this deletes data.' No additional behavioral traits are disclosed, such as irreversibility, required permissions, or side effects beyond what annotations cover.

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 with the main action. The second sentence about destructiveness is somewhat redundant with annotations but serves as a clear warning; however, it adds little for an AI agent and could be considered fluff.

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 bulk delete operation, the description lacks essential context about the request body, such as expected fields or format. Although an output schema exists, the input semantics remain unexplained, making the tool difficult to use correctly without additional documentation.

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 input schema has one generic 'body' object with no description, and the schema description coverage is 0%. The description does not mention what the body should contain (e.g., a list of blocklist IDs), leaving the agent without sufficient information to construct a valid request.

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 a specific verb ('Bulk delete') and resource ('blocklisted releases'), clearly indicating the action and target. The word 'bulk' distinguishes it from the sibling tool radarr_delete_blocklist, which suggests a single-entry deletion.

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 such as radarr_delete_blocklist for a single entry. The description does not mention any conditions, exclusions, or context where this tool should or should not be used.

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