radarr_create_rootfolder

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

Annotations already indicate readOnlyHint=false, so the tool is known to be a write operation. The description adds a 'WRITE: this modifies your Radarr instance' callout, which reinforces this but offers little beyond the annotation. It does not disclose specifics about what gets modified, potential side effects, or error conditions, but with annotations present, a moderate score is appropriate.

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 sentences and front-loaded with the core purpose. The write warning is placed after the main action, making it easy to parse. However, it is too sparse to earn a 5, as the 'WRITE' note is somewhat redundant with annotations and the description lacks valuable details.

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 create operation with a generic 'body' parameter and no schema descriptions, the description is inadequate. It does not explain what a root folder is, what fields are needed, or how to validate the request. While the output schema exists, the input side remains unexplained, making this incomplete for real-world use.

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 has one parameter 'body' with no description, default {}, and additionalProperties=true. Schema coverage is 0%, so the description must compensate. However, the description says nothing about what the body should contain (e.g., path, name) or how to structure the request. This leaves users completely in the dark about parameters.

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 'Create root folders' with a specific verb and resource. This distinguishes it from sibling tools like radarr_list_rootfolder, radarr_get_rootfolder, and radarr_delete_rootfolder, which have different actions.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that you should use this when you need to add a new root folder to Radarr, nor does it reference sibling tools or prerequisites. The only additional note is a write warning, which is not usage guidance.

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