delete_root_folder

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

No annotations are present, so the description carries the safety burden. The 'Files on disk are not touched' statement is a valuable disclosure that the operation is non-destructive to media files, but it does not reveal other meaningful behavioral traits such as whether the removal is reversible or what happens to series that reference the root folder.

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 entire description is two short sentences, front-loading the action and then adding the key caveat. Every word earns its place; there is no filler or 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 one-parameter delete operation with no output schema, the description covers the core action and the most important side-effect: files on disk are untouched. It still leaves some uncertainty about consequences for series assigned to the root folder and about response or error behavior, so it is adequate but not fully complete.

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 single required parameter id is already fully documented in the schema as 'Root folder id', and schema description coverage is 100%. The description adds no parameter-level detail, but none is needed beyond the schema. 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 uses the explicit verb 'Remove' and names the exact resource 'root folder' within Sonarr, which clearly distinguishes it from sibling operations like add_root_folder, list_root_folders, and get_root_folder. It also adds the important scope that files on disk are untouched.

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 implies the tool is appropriate when a root folder should be removed from Sonarr's configuration, and the 'Files on disk are not touched' caveat suggests it is not the tool for deleting actual media files. However, it never names sibling tools or explicitly states when not to use it, leaving selection largely to inference from the tool name.

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