radarr_bulk_delete_movie

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

The annotation destructiveHint=true already indicates the destructive nature. The description's 'DESTRUCTIVE: this deletes data' adds no new information beyond the annotation, and fails to clarify what exactly is deleted (e.g., database entries vs files) or if confirmation is needed.

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 appropriately short and front-loaded, but the second sentence repeats the destructiveHint annotation, making it redundant for an agent and thus not fully earning its place.

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, this description is severely inadequate. It does not explain the request structure, selection criteria, side effects, or any prerequisites, making it impossible for an agent to correctly invoke the tool.

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 a single generic 'body' object with no property descriptions and 0% schema_description_coverage. The description does not explain what the body should contain, leaving the agent without guidance on how to specify which movies to delete.

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 'Bulk delete movies' uses a specific verb and resource, clearly distinguishing it from 'radarr_delete_movie' (singular) and 'radarr_bulk_delete_moviefile' (files). The purpose is immediately clear.

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 vs alternatives. It does not mention that this is for multiple movies, nor does it reference radarr_delete_movie for single deletions.

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