radarr_bulk_update_movie

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

The description adds a 'WRITE: this modifies your Radarr instance' warning, which is useful but largely redundant with annotations (readOnlyHint: false). It doesn't disclose additional behavioral traits such as idempotency, required permissions, or potential impact on existing data beyond the annotation's implication.

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 brief with no filler, but it sacrifices essential details. It is appropriately front-loaded, but the second sentence is redundant with annotations. Still, it earns high marks for efficiency.

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 bulk write operation, the description lacks critical context: what fields can be updated, how movies are identified, whether the operation is reversible, and what the response looks like. Despite having an output schema, the input body is completely opaque.

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 schema has one 'body' parameter with no description and 0% schema description coverage. The description provides no information about what the body should contain, expected fields, or format. It completely fails to compensate for the schema's generic additionalProperties: true.

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 phrase 'Bulk update movies' uses a specific verb and resource, clearly distinguishing it from sibling tools like radarr_update_movie (singular) and radarr_bulk_update_moviefile (different entity). It states exactly what the tool does.

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 like radarr_update_movie or radarr_bulk_update_moviefile. There is no mention of exclusions, prerequisites, or use cases.

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