sonarr_delete_season

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

With no annotations, the description fully discloses destructive behavior and the important caveat that hardlinked files are not freed until the torrent is removed. This goes beyond basic expectations.

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 tightly written sentences with no redundancy. The first sentence states the core purpose, the second explains the key parameter, and the third adds a behavioral nuance. 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?

Covers the essential aspects: purpose, destructive nature, dry-run, and hardlink limitation. An output schema exists but is not shown; the description doesn't explain return values or prerequisites (e.g., series must exist). Given the minimal complexity, it is nearly complete.

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 adds crucial meaning for the confirm parameter (dry-run vs actual delete). The series_id and season_number are left to their names, which are self-explanatory in context, though examples or range hints would improve clarity.

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 explicitly states it deletes all episode files of a single season, using specific verb and resource. It distinguishes from sibling tools like sonarr_delete_episode_file and sonarr_delete_series by targeting a whole season.

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?

Clearly explains the dry-run mode using the confirm parameter, and notes that only one season is handled per call. However, it does not provide explicit when-not-to-use guidance or compare with alternatives.

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