radarr_import_list_movie

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

The annotations (readOnlyHint=false, destructiveHint=false) already convey that this is a non-destructive write. The description's 'WRITE: this modifies your Radarr instance' merely restates that annotation without adding new behavioral context such as duplicate handling, import trigger behavior, or side effects.

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 appropriately brief and front-loaded, with the action stated first and a safety note second. It is efficient, though the WRITE sentence is redundant with the annotations.

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?

Although an output schema exists, the tool performs a non-trivial import operation with an entirely undocumented body parameter. The description gives no context about what the import does, how it affects existing movies, or how the body should be structured, making it incomplete for safe 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?

The only parameter, 'body', has 0% schema description coverage and an empty items schema ({}) that provides no meaning. The description does not explain what the body array should contain (e.g., movie IDs, list IDs), failing to compensate for the schema gap.

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 clear action ('Import movies from an import list') with a specific verb, object, and source, and the WRITE flag reinforces intent. It inherently distinguishes from the sibling radarr_list_importlist_movie (listing vs. importing), though it does not explicitly name that 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?

No guidance is given on when to use this tool or when to prefer alternatives. The description lacks prerequisites, context about triggering an import, or any mention of related tools like radarr_list_importlist or radarr_action_importlist.

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