sonarr_delete_rootfolder

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

Annotations already declare destructiveHint=true, and the description merely repeats 'DESTRUCTIVE: this deletes data' without adding new behaviors. It does not specify what data is deleted (e.g., the folder record only vs. files on disk) or if the action is reversible.

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 two short sentences with no unnecessary words. It front-loads the purpose and then adds a clear warning, making it appropriately concise and well-structured.

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 destructive operation, the description is too vague. It lacks context about the scope of deletion, potential side effects, and safe usage conditions. The output schema does not compensate for this missing operational 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 'id' parameter is not described in either the schema or the description. With 0% schema coverage, the description should have explained that 'id' refers to the root folder ID, but it does not, leaving the parameter semantics unclear.

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 'Delete root folders' with a specific verb and resource. It is unambiguous and distinguishes itself from sibling tools like sonarr_list_rootfolder, sonarr_create_rootfolder, and sonarr_get_rootfolder by the destructive action.

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?

No guidance is provided on when to use this tool or when to avoid it. There is no mention of prerequisites, such as ensuring no series depend on the root folder, or alternatives like update operations.

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