delete_file

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly warns that this deletes real media and removes the file from the database, which is critical for a destructive operation. It does not mention irreversibility explicitly, but 'deletes real media' strongly implies permanence.

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 deliver the core action, the resource affected, and the critical user-confirmation warning. No filler or redundancy, and the most important behavioral warning is placed at the end for emphasis.

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 single-parameter destructive tool with a fully documented schema, the description is nearly complete. It covers what the tool does, that it affects real media, and that confirmation is required. The only minor gap is not explicitly stating the operation cannot be undone, though this is strongly implied.

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 provides 100% coverage, documenting file_id as the full path from search_files. The description does not add additional parameter-level meaning, so the baseline score of 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 states a specific action ('Delete one file from disk') and a specific resource (file, Tdarr database), and clarifies this is the single-file variant as opposed to bulk deletion. The API endpoint is also included, making the tool's intent 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?

The description clearly implies this is for deleting a single file and explicitly instructs to confirm with the user first. However, it does not mention alternatives such as bulk_delete_files or delete_unhealthy_files, so an agent gets no explicit guidance on when to choose this over sibling tools.

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