radarr_add_movie

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

The description is minimal and does not disclose significant behavioral traits. Annotations indicate it is a write operation (readOnlyHint=false) and not destructive, but the description does not mention potential side effects such as automatically searching for the movie (searchForMovie defaults to true) or that it may download metadata. This lack of behavioral context is a notable gap for a mutation tool.

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 a single, clear sentence that is front-loaded and free of any fluff. It efficiently conveys the tool's purpose without unnecessary details.

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 tool's complexity (7 parameters, no output schema) and its side effects, the description is too sparse. It does not explain what happens after adding (e.g., whether the movie is monitored, searched for, or what a successful response contains). This incompleteness leaves the agent without important runtime context.

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 provides 100% coverage of all 7 parameters with clear descriptions, defaults, and enums. The description adds no extra parameter information beyond what the schema already offers, so it meets the baseline of 3.

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 tool adds a new movie to Radarr using TMDB ID, with a specific verb ('Add'), resource ('movie to Radarr'), and method ('by TMDB ID'). This distinguishes it from sibling tools like radarr_search and radarr_get_movies.

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?

The description implies its usage (adding movies to Radarr) but provides no explicit guidance on when to use it versus alternatives, nor any prerequisites or exclusions. The tool name and sibling list offer some implied context, but no direct comparison or when-not-to-use guidance is given.

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