sonarr_import_series

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

The description explicitly labels the operation as 'WRITE' and states it modifies the Sonarr instance, which adds a safety-relevant signal beyond the existing annotations. However, it does not disclose more specific behavioral traits such as idempotency, potential side effects, or required permissions, leaving some gaps.

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 very concise, with two short sentences that front-load the main action and provide a necessary write-safety note. There is minimal repetition of schema or annotation content, though the second sentence slightly overlaps with the existing annotations.

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?

Given the minimal schema and the complexity of importing a list of series resources, the description is under-specified. It does not explain what constitutes a series resource, how to handle existing entries, or any import-specific details. The presence of an output schema helps on the response side, but the request construction is not sufficiently addressed.

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 schema has only one parameter (body) with 0% description coverage, so the description's clarification that body is 'a list of series resources' is valuable. Yet it fails to elaborate on the required fields or structure of each series resource, offering only a high-level hint.

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 uses a specific verb+resource structure ('Import series') and clarifies the payload is a list of series resources. It is clear about the basic operation, though it does not differentiate from sibling tools like sonarr_add_series, leaving some ambiguity about the exact import semantics.

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 is provided on when to use this tool versus alternatives such as sonarr_add_series. There is no mention of prerequisites, exclusions, or contextual triggers, so the agent must infer the appropriate usage context.

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