sonarr_add_series

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

Annotations already state readOnlyHint=false and destructiveHint=false. The description repeats "WRITE: this modifies your Sonarr instance," which adds no new behavioral insight. It does not disclose side effects like triggering scans, duplicate handling, or required permissions. The body-type note is about input structure, not behavior.

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 short sentences, front-loaded with the core purpose. The parenthetical and WRITE note are succinct and add relevant information without verbosity.

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?

With a single generic body object and 0% schema coverage, the description is insufficient for an agent to construct a valid request. It does not mention how to obtain a SeriesResource schema or prerequisites, leaving a significant gap. The existence of an output schema is helpful but not shown, and the description does not compensate for the opaque input.

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 0%, so the description must compensate. It states "body is a SeriesResource," which gives a type reference but no field-level details, required properties, or examples. This is a minimal compensation for an opaque body parameter.

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 series to Sonarr," with a specific verb and resource. It also specifies the body type (SeriesResource), which distinguishes it from update/import operations and gives immediate clarity on what the tool does.

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_import_series. It lacks prerequisites (e.g., required root folder, quality profile) or any context for when this operation is appropriate. The WRITE warning indicates a side effect but does not help with selection.

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