sonarr_get_series_folder

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

The annotation readOnlyHint: true covers the safety profile, and the description's 'Fetch' is consistent with a read-only operation. However, the description adds no extra behavioral context (e.g., errors, response shape), but the annotation lowers the burden.

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?

A single sentence that is direct and front-loaded. No wasted words; the core action and resource are stated immediately.

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?

Although simple, the description omits key context: the tool name suggests 'folder' but the description only mentions 'series', and there is no differentiation from 'sonarr_get_series'. The output schema exists, so return values are covered, but usage context is missing.

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. 'By id' indicates the 'id' parameter identifies the series, but it does not explicitly state it is the series ID or describe any constraints. For a single integer parameter, this is minimally adequate.

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 'Fetch a single series by id' has a clear verb and resource, but the tool name references 'series_folder' while the description says 'series', creating ambiguity about the actual resource. It also fails to distinguish this tool from sibling 'sonarr_get_series'.

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 usage guidance is provided. The description does not indicate when to use this tool over 'sonarr_get_series' or 'list_series', nor does it mention any exclusions or prerequisites.

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