sonarr_purge_season

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

No annotations provided, but the description fully covers behaviors: destructive action, cross-seed inclusion, torrent location via history downloadIds, and effects of include_loose_matches and delete_torrent_files. The dry-run capability is also disclosed.

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 concise with two paragraphs: a summary first, then details on how torrents are located and parameter behavior. Every sentence adds value without 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?

Given the complexity of multi-system purge with cross-seeds and options, the description covers all key aspects. An output schema exists, so return values need not be explained. The description is adequate for an agent to invoke 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 coverage is 0%, but the description explains three of five parameters: confirm (dry-run vs execute), include_loose_matches (drops name/release-matched siblings), and delete_torrent_files (deletes from disk). series_id and season_number are self-explanatory from the tool name and context.

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 tool purges a whole season by deleting episode files in Sonarr and removing matching torrents in qBittorrent, including cross-seeds. It distinguishes itself from siblings like sonarr_delete_season and radarr_purge_movie by specifying the multi-system cleanup.

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 explains the dry-run mechanism with confirm and details on options like include_loose_matches and delete_torrent_files. However, it does not explicitly state when to use this tool over alternatives (e.g., sonarr_delete_season for Sonarr-only cleanup), leaving some ambiguity.

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