sonarr_monitor_episode

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

Annotations already indicate readOnlyHint=false, so the explicit 'WRITE' warning is somewhat redundant. However, it does reinforce that this is a modifying operation, which is useful. No additional context such as permissions, side effects, or what happens to episodes is disclosed.

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 exceptionally concise: one sentence for the action plus a brief WRITE warning. It is front-loaded with the main purpose and contains no fluff.

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?

The output schema covers return values, so the description need not explain them. The description covers the core action and body format. The only gap is the unexplained include_images parameter and a lack of context on when to use monitoring versus unmonitoring. Overall, it is fairly complete for a simple tool.

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 description explains that 'body is an EpisodeResource[] of id/monitored pairs', which is crucial because the schema only defines body as a generic object without a description. However, the second parameter, include_images, is not mentioned at all, leaving its purpose unexplained.

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 begins with 'Monitor or unmonitor episodes', clearly stating the verb and resource. It further clarifies that the body consists of 'id/monitored pairs', distinguishing it from generic episode update tools like sonarr_update_episode.

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 provides no guidance on when to use this tool versus alternatives like sonarr_update_episode. It only states that it modifies the Sonarr instance, which is a behavioral note, not usage guidance. No exclusions or alternative recommendations are given.

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