radarr_add

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

No annotations are provided, so the description carries the full burden. It clearly states that by default it starts searching for a release immediately and requires user confirmation, which is helpful. However, it does not disclose potential side effects like whether existing movies are overwritten, or auth/permission needs.

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 two sentences and immediately states the core action. The second sentence provides crucial usage guidance. It is efficient, though the first sentence could be slightly more front-loaded with the behavioral note.

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 has 6 parameters, high schema coverage, and no output schema, the description covers the key semantic behavior (immediate search, user confirmation). It does not explain return behavior, but with no output schema that is less critical. Still, for a tool with moderate complexity it is fairly complete.

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 high at 83%, so the schema already documents most parameters. The description adds no extra parameter details beyond what is in the schema, so a baseline score of 3 is appropriate.

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 uses a clear verb-resource pair ('Add a movie to Radarr') and explicitly distinguishes from siblings by mentioning the default start of release searching, which is a key differentiator from radarr_lookup or radarr_grab.

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 states it requires user confirmation before calling, which guides the agent on preconditions. However, it does not explicitly compare to sibling tools like sonarr_add or radarr_grab, nor does it specify when not to use it.

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