radarr_update_movie

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

The description indicates this is a write operation, but readOnlyHint=false already communicates that. No extra behavioral details are disclosed, such as the effect of move_files or whether the update triggers a rescan. The description adds minimal value 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 very short and front-loaded, with no filler. However, the second sentence ('WRITE: this modifies your Radarr instance') is largely redundant with the annotations, and the overall brevity sacrifices critical information.

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?

This tool has three parameters including a nested body object, yet the description provides no context about the data structure, the purpose of move_files, or the expected behavior of the update. Even with an output schema, the input semantics are entirely missing, making it inadequate for correct invocation.

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?

Schema description coverage is 0%, and the description does not mention the id, body, or move_files parameters. The description completely fails to compensate for the lack of schema documentation, leaving the agent without any semantic guidance for the parameters.

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 'Update movies', which is a clear verb+resource pair, but it is vague about what aspects of a movie can be updated. It does not distinguish this from sibling tools like radarr_update_moviefile or radarr_bulk_update_movie.

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 radarr_bulk_update_movie or radarr_update_moviefile. The only addition is a generic 'WRITE' warning, which does not help the agent decide when to invoke this tool.

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