sonarr_update_series

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

The description labels the operation as 'WRITE' and states it modifies the Sonarr instance. While this is consistent with `readOnlyHint=false`, it adds little beyond what annotations already imply, and provides no detail on side effects, reversibility, or whether file moves are involved.

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?

At two sentences, it is brief and front-loaded, but the second sentence is largely redundant with the annotations. It is concise but sacrifices informational value, earning a mid-range score.

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?

For a tool with a flexible 'body' parameter and a write operation, the description is under-specified. It lacks context about the update process, expected input structure, and ordering relative to bulk operations. The presence of an output schema compensates for return values, but overall the description is incomplete.

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 description offers no parameter semantics. With 0% schema description coverage, the 'body' object remains undefined, and the agent is left without any guidance on the required or optional fields for the update.

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 states 'Update series' with a clear verb and resource, distinguishing it from other update tools targeting different resources. However, it does not differentiate it from `bulk_update_series` or clarify what updating entails, so it is clear but not fully specific.

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 given on when to use this tool versus alternatives such as `bulk_update_series` or the many other update tools. There is no mention of prerequisites, appropriate contexts, or exclusions, leaving the agent to infer usage from the name.

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