sonarr_set_season_monitoring

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

With no annotations, the description sufficiently discloses key behaviors: it's reversible, does not trigger a download ('no immediate grab'), and returns the new state. This helps agents understand the side effects and safety profile without additional context.

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 three concise sentences. The first sentence states the core purpose, the second adds a key behavioral note, and the third specifies the return value. No unnecessary words; 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 the low parameter count and the presence of an output schema, the description covers the essential behavioral context but fails to document parameter semantics. Combined with 0% schema coverage, this leaves ambiguity in parameter usage, making it incomplete for first-time use.

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?

The input schema has 0% description coverage, yet the description provides no explanation for the three parameters (series_id, season_number, monitored). While the parameter names are somewhat self-explanatory, the description does not clarify details like expected formats or zero-based indexing, which would be helpful for correct invocation.

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 action: 'Enable or disable monitoring for a single season of a series.' This is a specific verb-resource pair, and it distinguishes itself from sibling tools like sonarr_delete_season or sonarr_search_season by focusing on the monitoring state toggle.

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 mentions the action is reversible and doesn't require confirmation, but provides no guidance on when to use this tool versus alternatives like sonarr_delete_season or sonarr_purge_season. It lacks explicit when-to-use or when-not-to-use information.

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