sonarr_update_episode

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

The description explicitly labels the tool as WRITE and states it modifies the Sonarr instance, which reinforces the readOnlyHint: false annotation. However, it does not disclose specific effects, reversibility, or required permissions, so it adds only minimal behavioral context beyond the annotations.

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 concise with two short sentences, each carrying useful information. It is front-loaded with the core action and then a clear write warning. However, it is too sparse to fully cover the tool's needs, which is a trade-off but still appropriate for the dimension.

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 presence of a nested body object and an output schema, the description fails to explain how to construct a valid update request, what the body should contain, or how this tool relates to episode management siblings. It is incomplete for a write operation with rich parameters.

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?

With 0% schema description coverage, the description must compensate, but it provides no explanation of the 'id' parameter or the 'body' object. The agent cannot infer what fields are updatable or how to construct the body, leaving parameter semantics almost entirely undocumented.

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 'Update episodes' with a specific verb and resource. However, it does not differentiate from sibling tools like update_episodefile or monitor_episode, so it lacks scope details. It is clear enough but not distinctive.

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?

No guidance is provided on when to use this tool versus alternatives such as sonarr_monitor_episode or sonarr_update_episodefile. There are no usage contexts, prerequisites, or exclusions.

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