sonarr_series_seasons

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

No annotations are provided. The description indicates a read-only operation ('Show'), but does not explicitly confirm non-destructive behavior, required permissions, or other side effects. It relies on the verb to imply safety.

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 sentences: first states the core purpose, the second details output fields. No redundant information, front-loaded, and easy to parse.

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 simple read tool with an output schema (present, not shown), the description covers what the agent needs: purpose, input, and output content. It leaves no obvious gaps.

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 0%, so the parameter 'series_id' is only described by its name and type. The description adds context that it refers to a tracked series, but does not explain how to obtain the ID (e.g., from sonarr_list_series). This is adequate but not exemplary.

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 shows a 'season-by-season breakdown of an already-tracked series', with specific output details. This differentiates it from siblings like sonarr_list_series (list all series) and sonarr_season_episodes (episodes of a specific 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 description implies the tool is for series already in Sonarr ('already-tracked'), but does not explicitly state when not to use it or mention alternatives. It lacks guidance on distinguishing from other season-related tools like sonarr_search_season.

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