tdarr_bulk_delete_files

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

With no annotations, the description states the tool deletes from both disk and database, which is basic behavioral disclosure. However, it omits details about irreversibility, permission needs, or error states, which would be valuable for a destructive bulk operation.

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 a single, concise sentence with no unnecessary words. It front-loads the key action, and every word earns 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?

Given the simple parameter set and no output schema, the description is minimally adequate but lacks details on bulk limits, error handling, or confirmation steps. For a destructive tool, more completeness would improve usability.

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?

Schema coverage is 100% and the parameter 'fileIds' already has a description ('Array of file IDs to delete') in the input schema. The tool description adds no further meaning, so score is baseline 3.

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 uses 'Bulk delete selected files from disk and remove them from the database' which clearly specifies the verb (delete), resource (files), and scope (bulk). It distinguishes from siblings like tdarr_delete_file (single) and tdarr_delete_unhealthy_files (specific subset).

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 (e.g., tdarr_delete_file for single files). It lacks prerequisites, exclusions, or scenarios where it 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.