sonarr_delete_series

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

Explains dry-run behavior (confirm=false) and file deletion option (delete_files). No annotations provided, so missing behavioral traits like destructiveness or recovery options. Adequate but not comprehensive.

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?

Three sentences, purpose first, no fluff. Every sentence adds value.

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 no annotations and 0% schema coverage, description covers key behavioral aspects. With output schema present, return values may be documented there. Slightly incomplete regarding side effects.

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 description must compensate. Adds meaning to confirm (dry-run) and delete_files, but does not mention series_id. Two out of three parameters explained, partially compensates.

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?

Clearly states verb 'delete', resource 'series', and method 'by its internal id'. Distinguishes from sibling tools like sonarr_delete_season and sonarr_delete_episode_file.

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?

Provides clear context on when to use confirm and delete_files parameters. Does not explicitly state when not to use or alternatives, but purpose is straightforward.

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