sonarr_update_season_pass

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

Annotations already indicate readOnlyHint=false, which tells the agent this is a write operation. The description's 'WRITE: this modifies your Sonarr instance' only repeats that fact without adding new behavioral context such as permissions, idempotency, or side effects. No additional transparency is provided.

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 two sentences and front-loads the primary purpose. The second sentence about WRITE is somewhat redundant given the annotations, but it's not verbose. It is clean and efficiently worded.

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?

Despite the presence of a nested body object and no schema descriptions, the description is minimal and does not explain what season pass settings are, how they affect monitoring, or the structure of the response (even if an output schema exists). It leaves the agent with significant gaps for a non-trivial write operation.

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 provides a single 'body' object with 'additionalProperties: true' and no descriptions (0% coverage). The description compensates by specifying that the body is a 'SeasonPassResource', giving essential type information. However, it doesn't enumerate fields within that resource, so some ambiguity remains.

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 'Apply season pass monitoring settings' clearly states a specific action (apply) on a specific resource (season pass), distinguishing it from sibling tools like update_series or update_episode. The explicit 'WRITE' note reinforces that this is a modifying operation, but the core purpose is unambiguous.

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 this tool is for changing season pass monitoring settings, but it does not explicitly state when to use it versus alternatives (e.g., updating individual series). No exclusions or alternative tool names are provided, so guidance is merely implied.

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