radarr_bulk_delete_moviefile

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

The description explicitly warns 'DESTRUCTIVE: this deletes data,' which reinforces the destructiveHint annotation. However, it adds no additional behavioral context such as permanence, required permissions, or recovery options. Since annotations already cover the destructive safety profile, the added value is minimal but not zero.

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 concise and front-loaded, with the action stated first. The warning earned its place. It is slightly under-specified for a destructive tool, but as far as structure and efficiency, it is well-formed.

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, the description is incomplete. It does not clarify what 'bulk' means, how to specify which files to delete, or what the request body should look like. Even though an output schema exists, the lack of parameter documentation and usage context leaves significant gaps.

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 additionalProperties true, and the description provides zero parameter information. With schema description coverage at 0%, the description fails to compensate. The agent has no idea what the body should contain (e.g., list of movie file IDs).

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 'Bulk delete movie files' with a specific verb and resource. The 'bulk' qualifier distinguishes it from the singular 'radarr_delete_moviefile' sibling, making the purpose unambiguous.

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. It does not mention the singular delete tool, nor does it explain what 'bulk' implies (e.g., multiple IDs, prerequisites). The agent gets no decision support.

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