Sonarr: List Series

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

Annotations already declare readOnlyHint=true, and the description adds behavioral details beyond that: default slim fields, paging is server-side, and that verbose returns heavier data. No contradictions; description enriches annotation context.

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?

Description is moderately concise, front-loading purpose and then listing fields and notes. Every sentence adds value, though the field list is somewhat long. No wasted words, but could be shortened slightly.

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?

Despite no output schema, the description explains the return fields in detail (listing slim fields and noting what verbose adds). Also covers paging behavior and sibling tools. Highly complete for a paged list tool.

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?

Input schema has 100% coverage, and the description adds context for each parameter: page default 1, page_size default 50 max 200, verbose meaning and side effects. The hint to use smaller page_size with verbose adds value beyond schema.

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 it lists TV series tracked by Sonarr as a paged result, and distinguishes from 'sonarr_get_series' (full details) and 'sonarr_lookup_series' (find untracked). The verb 'list' plus resource and paging detail make the purpose highly specific.

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?

Provides explicit guidance on when to use this tool (listing series) and when not ('For full details on one series, use sonarr_get_series' and 'To find a series NOT yet tracked, use sonarr_lookup_series'). Also gives tips on page_size versus verbose to avoid MCP cap.

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