delete_series

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently states the main effect and the two optional destructive behaviors: deleting files from disk and adding an import list exclusion. However, it does not mention irreversibility, return behavior, or what happens to the series record if delete_files is false, which are meaningful gaps for a delete operation.

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?

A single well-structured sentence that front-loads the core action and appends the optional behaviors in a logical order. Every phrase contributes meaning, including the rationale for the import list exclusion ('so lists do not re-add it'). There is no filler or redundancy.

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 straightforward delete tool with a fully documented schema, the description covers the primary action and all optional side effects. It is missing an explicit irreversibility warning and a direct contrast with the bulk delete sibling, but the provided information is otherwise sufficient for an agent to understand what the tool does and invoke it correctly.

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 description coverage is 100%, so the baseline is 3. The description conceptually maps to the optional parameters—delete_files and add_import_list_exclusion—but it adds no semantic detail beyond what the schema already provides. The required id parameter is not elaborated on, but the schema already documents it clearly.

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 uses a specific verb and resource: 'Remove a series from the library.' It clearly states the core action and the optional side effects—deleting files and adding an import list exclusion. It does not explicitly contrast with delete_series_bulk, but the singular 'a series' implies single-series operation, which is enough to differentiate from the bulk sibling.

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?

The description gives no explicit guidance about when to use this tool versus alternatives like delete_series_bulk or delete_episode_file. It implies use when removing a single series, but it does not state the condition for choosing the bulk variant or any exclusions, leaving the agent to infer selection criteria from the name alone.

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