set_episodes_monitored

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly communicates that the tool toggles the monitored state for selected episodes, but it adds no further context such as permissions, side effects, or reversibility. For a simple state toggle this is adequate but not rich.

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 core action is front-loaded and the sibling alternative is provided immediately after, making the tool easy to process quickly.

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 two-parameter mutation with no output schema, the description and schema together give an agent everything needed to select and invoke the tool correctly. It states the action, the scope, and the key alternative without unnecessary detail.

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 already documents both parameters with 100% coverage, including the boolean meaning and the Sonarr episode ids. The description adds only the framing of 'individual episodes,' which aligns with but does not meaningfully extend the schema. Baseline 3 is appropriate.

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 states a specific verb-resource pair: 'Monitor or unmonitor individual episodes.' The word 'individual' clearly distinguishes it from season-level operations, and the sibling set confirms set_season_monitored is the related alternative.

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 explicitly tells the agent when to use an alternative: 'Use set_season_monitored for whole seasons.' This gives a concrete routing rule and implies this tool is for episode-level granularity only.

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