radarr_delete_moviefile

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

The annotation destructiveHint: true already indicates the operation is destructive. The description's 'DESTRUCTIVE: this deletes data' simply restates that without adding new behavioral context like permanence, cascading effects, or required permissions. It does not contradict annotations but adds no extra transparency.

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, making it appropriately concise and front-loaded with the warning. The second sentence is somewhat redundant given the annotations, but it does not waste words. Overall, it is efficient.

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 simple delete operation, the description is minimally viable: it states the action and warns about data loss. However, it omits details about the parameter, any side effects, or when to use it. Given the output schema exists and annotations are present, the description is partially complete but not thorough.

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 description does not explain the id parameter, and the schema provides no description for it (coverage 0%). While the tool name and parameter type suggest it is the movie file's ID, the description lacks explicit clarification. This is a noticeable gap for a single-parameter tool.

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 tool deletes movie files, using a specific verb and resource. It is distinct from sibling tools like radarr_list_moviefile and radarr_bulk_delete_moviefile by its focus on deletion. The tool name reinforces the singular scope.

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?

The description provides no guidance on when to use this tool versus alternatives such as radarr_bulk_delete_moviefile. There is no mention of prerequisites, contexts, or exclusions. The destructive warning is behavioral, not usage guidance.

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