Sonarr: Edit Series

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

The description adds valuable behavioral details beyond annotations: the internal GET+PUT process, preservation of unchanged fields, and explicit warning about root_folder_path moving files. Annotations already indicate destructive hint, but description adds specific context.

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?

Three well-structured sentences: purpose, process/guidance, and warning. No 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?

Covers essential aspects (process, side effects, parameter usage) for a simple edit tool. No output schema but return values are likely straightforward given the operation. Minor gap: doesn't mention if the full updated resource is returned.

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 coverage is 100%, so baseline is 3. Description adds useful group-level guidance ('pass only fields you want to change') and clarifies tags behavior ('full replacement, not append'), raising it to 4.

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 'Edit settings on an existing Sonarr series' with a specific verb and resource, and it distinguishes from sibling tools like sonarr_add_series and sonarr_get_series.

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?

Provides clear context: internally GETs and PUTs, pass only changed fields, and warns about root_folder_path moving files. However, it does not explicitly state when not to use this tool or list alternatives, so a 4 is appropriate.

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