Sonarr Get Series

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

No annotations provided, so description bears full responsibility for behavioral disclosure. The description only says 'list' or 'return,' implying read-only behavior, but does not confirm safety, mention rate limits, or describe pagination despite multiple parameters (page, limit, cursor). No details on what 'return one series' entails (e.g., full details vs summary).

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 succinct with two sentences, front-loading the primary function. However, given the complexity (11 parameters, many sibling tools), it is possibly over-concise, sacrificing necessary detail for brevity.

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 has 11 parameters, zero schema coverage, no output schema, and no annotations. The description fails to provide enough context for proper usage, such as parameter formats, pagination details, or return value structure. The agent would have difficulty using this tool effectively.

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% for 11 parameters. The description adds no meaning to any parameter. Even basic parameters like 'id' or 'page' are not explained. Without explanation, the agent cannot know how to use parameters correctly, especially optional ones like 'fields', 'detail', or 'cursor'.

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?

Description clearly states the tool lists Sonarr series or returns one series when an id is provided. It distinguishes two modes (list all vs single retrieval). However, it does not differentiate from sibling tools like sonarr_get_episodes or sonarr_get_missing, which could be confused.

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 guidance on when to use this tool versus alternatives. There are many sibling tools (e.g., sonarr_get_episodes, sonarr_get_missing) but no indication of which to choose based on the user's goal. No context about prerequisites or when to supply an id.

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