radarr_bulk_update_moviefile

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

The annotations already indicate a write operation (readOnlyHint false), and the description adds an explicit 'WRITE' warning stating it modifies the Radarr instance. This is consistent with annotations but adds little beyond them. It does not disclose side effects, reversibility, or what exactly is modified, so behavioral transparency is limited but not contradictory.

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 extremely concise: two short sentences with the main action front-loaded and no unnecessary words. The WRITE warning is relevant and earns its place. It is appropriately sized for the minimal information it conveys.

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 having an output schema, the input side is entirely opaque: the body parameter is unspecified, and the description does not explain what 'update' does, what fields are affected, or any prerequisites. For a bulk write operation, the description is severely incomplete and leaves the agent without enough context to invoke the tool correctly.

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 has one parameter, 'body', which is an array with empty item schema and no description. The description provides zero information about what the body should contain, and schema description coverage is 0%. With no compensation from the description, the agent has no understanding of the required payload structure.

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 the action (bulk update) and resource (movie files), which is a specific verb+resource pair. However, it does not distinguish from sibling tools like radarr_bulk_edit_moviefiles, and the exact meaning of 'update' is left unclear. The WRITE tag reinforces the operation type but does not add purpose differentiation.

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 given on when to use this tool versus alternatives such as radarr_update_moviefile or radarr_bulk_edit_moviefiles. The only additional note, 'WRITE: this modifies your Radarr instance,' is a warning rather than a usage guideline. There are no explicit use cases or exclusions.

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