sonarr_add_series

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

With no annotations, the description carries the full burden of disclosing side effects, but it only says 'Add a TV series' without detailing whether it overwrites existing entries, triggers any post-add actions, requires specific permissions, or returns a confirmation. No behavioral traits beyond the bare action are disclosed.

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 two concise sentences, with the purpose stated first and prerequisite mapping in the second. Every word contributes, and it is appropriately sized for the tool's complexity.

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 description provides important prerequisite context and leverages the 100% schema coverage, but it omits any information about return values, error behavior, or what happens if the series already exists. Given the absence of annotations and output schema, the description covers the minimum needed to gather inputs but leaves notable gaps in predicting the tool's response.

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 100%, so baseline is 3, but the description adds meaningful value by mapping parameters to their source tools (e.g., rootFolderPath from sonarr_get_root_folders, qualityProfileId from sonarr_get_quality_profiles). This clarifies not just what the parameters are, but how to obtain correct values, exceeding the schema's basic descriptions.

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 'Add a TV series to Sonarr' with a specific verb and resource, distinguishing it from sibling tools like sonarr_update_series and sonarr_delete_series. The action is unambiguous and immediately understood.

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?

It provides explicit prerequisite guidance by naming the exact preceding tools to use for each required parameter (sonarr_search, sonarr_get_root_folders, sonarr_get_quality_profiles, sonarr_get_tags). This is strong usage context, though it does not explicitly state when not to use the tool or mention alternatives in a comparative sense.

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