radarr_add_movie

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

With no annotations provided, the description must disclose behavioral traits. It explains that confirm=True actually adds, while False/omit does a dry-run. However, it does not mention idempotency, error handling, or what happens if the movie already exists.

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 only three concise sentences. The first states purpose, the second lists prerequisite tools, and the third explains the confirm behavior. No superfluous 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?

The description is fairly complete for a simple creation tool. It explains how to obtain all required parameters and the confirm behavior. However, it lacks details on whether duplicates are handled, permissions needed, or potential errors. Since an output schema exists, return values need not be described.

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%, so the description must compensate. It tells the agent to use specific sibling tools to obtain rmdb_id, quality_profile_id, and root_folder_path, giving semantic meaning beyond the schema. However, it does not describe the confirm parameter's type or default, which is already in schema, and does not elaborate on parameter constraints.

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 movie to Radarr by tmdbId. The verb 'Add' and resource 'movie' are specific, and it distinguishes from sibling tools like radarr_list_movies or radarr_delete_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?

The description explicitly tells the agent to use radarr_lookup_movie, radarr_quality_profiles, and radarr_root_folders to obtain the required parameters. It also explains the confirm parameter's role in performing a dry-run vs actual addition, providing clear when-to-use guidance.

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