sonarr_delete_episode_file

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

No annotations exist, so the description carries full burden. It discloses that the action is destructive, explains the dry-run preview, and notes that hardlinked files are not freed on disk until the torrent is removed. This adds useful behavioral context beyond the obvious.

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?

Three concise sentences front-loaded with purpose, followed by key details. No wasted words. Perfectly structured for quick comprehension.

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?

The description covers the action, id, confirm behavior, and disk-space nuance. With an output schema present, return values are handled. Could mention prerequisites or error cases, but overall adequate for a simple delete tool.

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 description coverage is 0%, so the description must compensate. It explicitly explains the confirm parameter (dry-run vs delete) which adds meaning beyond the schema. However, the episode_file_id parameter is only mentioned as 'by its id' with no guidance on how to obtain it.

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 it deletes a single episode file by its id, with the explicit label 'destructive'. This distinguishes it from sibling tools like sonarr_delete_queue_item, sonarr_delete_series, etc.

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 explains the dry-run vs actual delete behavior using the confirm parameter. However, it does not provide explicit guidance on when to use this tool over alternatives or mention prerequisites like obtaining the episode_file_id.

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