sonarr_get_all_series

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

No annotations are provided, so the description carries the full disclosure burden. It usefully describes the return shape ('complete list with metadata, seasons, and statistics'), which matters because there is no output schema, but it says nothing about read-only safety, pagination, response size on large libraries, or failure modes.

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 compact sentences, purpose front-loaded, with the return content following immediately. Nothing is padded or redundant.

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 zero-parameter read tool with no annotations and no output schema, the description is nearly sufficient: it covers scope and roughly what comes back. It stops short of noting anything about library-size behavior or that results are unfiltered and potentially large, which is the only meaningful gap.

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 takes zero parameters, so per the rubric the baseline is 4. The description correctly implies a parameterless full-library fetch and does not invent any filtering arguments.

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 names a specific verb and resource: 'Get all series in your Sonarr library.' The word 'all' plus the return payload distinguishes it implicitly from single-item siblings like sonarr_get_series and sonarr_get_series_by_tvdb, but it never explicitly contrasts with sonarr_search_series or the other list-style tools, so sibling differentiation is left to inference.

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 guidance, no condition under which this bulk-fetch should be preferred over sonarr_search_series or per-series retrieval, and no mention of alternatives. The 'all' phrasing hints at bulk enumeration but does not state the selecting condition.

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