bulk_delete_files

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

There are no annotations, so the description carries the full burden of disclosing destructive behavior. It clearly states that it 'deletes real media' and also removes records from the database, and alerts the agent to confirm with the user first. This is strong transparency for a destructive tool, though it stops short of stating irreversibility explicitly.

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?

Two tight sentences. The first states the action and scope, and the second delivers the crucial safety warning. No filler or repetition.

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 one-parameter destructive tool with no output schema, the description covers the essential details: what it deletes, that it also updates the database, and the required confirmation step. It could add information about irreversibility or expected response, but the definition is sufficient for safe invocation.

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 already documents file_ids as 'File IDs (full paths) to delete' with 100% coverage. The description reinforces that these are multiple files but adds no new parameter-level detail beyond what the schema provides. Baseline 3 is appropriate.

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 starts with a specific verb and resource: 'Delete several files from disk and remove them from the Tdarr database.' It clearly states the bulk nature of the operation, distinguishing it from single-file tools like delete_file. The endpoint is also included for clarity.

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 clear context: it is for deleting multiple files at once. It gives an explicit safety instruction ('list the files for the user and confirm before calling') which guides when and how to use it. It doesn't explicitly name alternatives like delete_file for single deletions, but the bulk context is unmistakable.

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