sonarr_add_series

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Add', without explaining idempotency, duplicate handling, error scenarios, or return value. While it mentions dependencies, the behavioral context is minimal for a write operation.

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 extremely concise, with three sentences that deliver critical usage guidance without any redundancy or filler. Every sentence adds value.

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 lack of output schema and annotations, the description adequately covers how to obtain all required parameter values from other tools. However, it does not explain the outcome of the addition (e.g., series created, episodes scheduled) or how optional parameters like monitored and seasonFolder behave. Still, it provides sufficient context for an agent to invoke the tool correctly.

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 input schema covers all parameters with descriptions (100% coverage). The description adds value by telling the agent which sibling tools to use to obtain each parameter's value (e.g., tvdbId from sonarr_search). This extra guidance improves parameter semantics beyond the 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 the action 'Add a TV series to Sonarr', which is a specific verb-resource pair. It distinguishes this tool from sibling tools like sonarr_search and sonarr_get_series by focusing on the creation operation.

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?

The description explicitly tells the agent to first use sonarr_search to find the tvdbId, and to use sonarr_get_root_folders, sonarr_get_quality_profiles, and sonarr_get_tags to obtain valid values for parameters. This provides clear prerequisites and when to use this tool versus alternatives.

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