sonarr_search_season

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

With no annotations, the description carries the full behavioral burden. It does disclose the key side effect — the season is sent to the download client, i.e. this triggers downloads rather than merely listing results — which is genuinely useful. However, it does not mention reversibility, duplicate-download risk for already-downloaded episodes, or the nature of the response.

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?

Two short sentences with no filler; the operation is front-loaded and the consequential side-effect sentence immediately follows. Nothing is wasted.

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 two-parameter command tool with complete schema descriptions and no output schema, the description covers the essential action and its main side effect. It is still thin on what happens next (queue behavior, confirmation, response content) given the absence of annotations.

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%: both seriesId and seasonNumber are documented in the schema. The description adds no format, range, or syntax detail beyond what the schema already provides, so the baseline 3 applies.

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?

States a specific verb (search) and resource (all episodes in a season), with scope that distinguishes it from the episode-level sibling sonarr_search_episodes. It does not explicitly name that sibling, so differentiation relies on the agent inferring scope from '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?

The phrase 'all episodes in a specific season' implies when this tool is appropriate versus an episode-level search, but no alternative is named and no exclusion (e.g., 'use sonarr_search_episodes for a single episode') is given. Usage is implied rather than stated.

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