radarr_delete_movie

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

Discloses dry-run capability via confirm parameter and file deletion option, but lacks details on permissions, irreversible consequences, or prerequisites. With no annotations, more behavioral context would be beneficial.

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?

Three sentences: first states purpose, second and third explain key parameters. No fluff, well-structured, and front-loaded.

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?

With output schema present, return values need not be explained. Covers key parameters and their effect, but could mention prerequisites (e.g., movie exists) and confirm that deletion is irreversible.

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 has 0% description coverage; description adds meaning for confirm (dry-run) and delete_files (file removal). movie_id is self-explanatory given purpose. Adds value beyond schema.

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?

Description clearly states the verb 'Delete', the resource 'a movie', and the method 'by its internal id'. It distinguishes from siblings like radarr_delete_movie_file that delete a specific file, not the whole 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?

Description mentions dry-run behavior and optional file deletion, but does not explicitly compare to alternatives like radarr_delete_movie_file or radarr_purge_movie, nor provide when-to-use or when-not-to-use guidance.

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