sonarr_delete_episode_file

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

With no annotations provided, the description carries the full burden. It discloses the destructive nature ('from disk') and the important behavioral outcome ('episode remains in Sonarr as unmonitored'), which goes beyond just stating the action. It does not mention irreversibility or permission requirements, but the key effects are covered.

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, well-structured sentence that front-loads the purpose and appends a parenthetical to explain the post-deletion state. Every word earns its place, with no redundancy.

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 delete operation, the description is quite complete. It explains the effect on disk and on the episode's monitoring status. It doesn't explicitly warn about irreversibility or list prerequisites, but these are largely self-evident given the schema and context. Sibling tool differentiation could be stronger, but overall it provides enough context.

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 input schema already provides a clear description for fileId ('from sonarr_get_episode_files'), and the schema coverage is 100%. The tool description adds no additional parameter meaning beyond what the schema already states, so the baseline 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 clearly states the action ('Delete a specific episode file from disk') and adds crucial context that the episode record remains in Sonarr as unmonitored. This distinguishes it from bulk deletion and other Sonarr tools.

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 word 'specific' implies this is for deleting one file at a time, and the existence of sonarr_delete_episode_files_bulk suggests an alternative, but the description does not explicitly say when to use this vs bulk deletion. It provides implied usage but no explicit guidance or exclusions.

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