sonarr_delete_series

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

With no annotations, the description must carry the burden of behavioral disclosure. It does indicate destructive behavior via 'remove' and 'delete files from disk', but it does not explicitly state that the action is permanent, whether permissions are required, or how it affects related data like episode history. It provides some transparency but lacks depth.

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, front-loaded with the core purpose and followed by optional flags. Every word earns its place, with no redundancy or fluff.

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 the low complexity of a simple delete operation and full parameter schema coverage, the description is adequately complete. It states the main function and both optional behaviors, which is sufficient for an agent to understand the tool's use. It lacks deeper context about consequences, but that is not critical for such a straightforward operation.

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?

All three parameters are fully described in the schema (100% coverage), so the baseline is 3. The description merely paraphrases the optional booleans ('Optionally delete files... add to import exclusions') without adding new technical semantics. It meets the baseline but does not exceed it.

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: 'Remove a series from Sonarr.' It also mentions optional behaviors (delete files, add to import exclusions) that differentiate it from other delete tools like sonarr_delete_episode_file or sonarr_bulk_delete_series. The verb and resource are specific and unambiguous.

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 such as sonarr_bulk_delete_series. It does not mention prerequisites, exclusions, or conditions under which this tool is appropriate, leaving the agent to infer usage solely from the name and description.

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