sonarr_get_root_folders

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

Without annotations, the description must carry the full burden. It does convey that this is a read-only retrieval of configuration (all root folders), and that these are storage locations for series. However, it does not disclose return format, whether it requires authentication, or if there are side effects. It exceeds the bare minimum but lacks depth.

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?

Two short sentences. The first sentence is the core action; the second adds useful context without being verbose. No wasted words, front-loaded with the main action.

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 tool is simple (no parameters, no output schema, no annotations), so the description does not need to explain return values or side effects. However, it could provide more context about what a root folder represents (e.g., filesystem paths) and when to use it relative to other series tools. As is, it is adequate but minimal.

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 tool has zero parameters, so according to the rules the baseline is 4. The description correctly does not discuss parameters, and it clarifies that the tool returns a list of all configured root folders, which is sufficient.

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 states a clear verb (Get) and resource (root folders) with scope 'all configured'. The second sentence adds meaning: root folders are storage locations for series. It does not explicitly differentiate itself from siblings like sonarr_get_series or sonarr_add_series, but the resource name is distinct enough.

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?

There is no explicit 'when to use' or 'when not to use' guidance. The phrase 'Shows where series can be stored' implies that it is useful before adding or moving series, but this is only implied and not stated. No alternatives are mentioned.

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