radarr_add_movie

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Add a movie', implying a create operation, but lacks details on authentication requirements, rate limits, whether duplicates are handled, or any side effects. This is insufficient 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 extremely concise with two short sentences, each earning its place. The first sentence states the core action, and the second provides a key usage hint. No wasted words.

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 complexity (7 parameters, no output schema, no annotations), the description is incomplete. It fails to explain how to obtain necessary parameter values (e.g., qualityProfileId, rootFolderPath) or what the expected outcome or errors are. The agent is left with significant information gaps.

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% for 7 parameters. The description adds minimal value beyond the schema by mentioning 'TMDB ID', which maps to one parameter (tmdbId). It does not explain other critical parameters like qualityProfileId, rootFolderPath, or searchForMovie, failing to compensate for the schema gaps.

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 ('Add a movie') and the resource ('to Radarr') using a specific identifier ('by TMDB ID'). It distinguishes from sibling tools like radarr_lookup_movie (lookup) and radarr_get_queue (queue management).

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 provides explicit sequential guidance ('Use radarr_lookup_movie first'), helping the agent understand the prerequisite step. However, it does not specify when not to use this tool (e.g., if movie already exists) or compare with alternatives beyond the lookup tool.

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