sonarr_bulk_update_series

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

Annotations already indicate a non-read-only and non-destructive operation. The description adds 'WRITE: this modifies your Sonarr instance,' which is largely redundant with readOnlyHint=false and lacks specific context about side effects, permissions, reversibility, or what exactly gets modified.

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 only one sentence plus a label, so it is concise with no fluff. However, it is under-specified for the complexity of the operation, making it not appropriately sized; it lacks both a clear purpose statement and parameter guidance.

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 that this is a bulk write operation with an open-ended body parameter and no schema descriptions, the description is severely incomplete. It fails to explain what the 'series editor' is, what fields can be updated, or how the bulk behavior works, making correct invocation nearly impossible.

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 has a single free-form 'body' object with no description and additionalProperties allowed. The description provides zero information about expected fields, format, or examples, leaving the agent with no guidance on how to construct a valid request.

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 says 'Update series editor' which names a specific Sonarr feature but doesn't explain what that entails or how it differs from single-series updates. The tool name includes 'bulk', but the description itself is vague about the resource and operation scope.

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 like sonarr_update_series or sonarr_bulk_delete_series. The description merely labels it as a write operation, with no mention of prerequisites, exclusions, or appropriate scenarios.

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