radarr_get_movie

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

No annotations are provided, so the description carries the burden. The 'Get' verb and the disclosure that results include file info, ratings, and collection data give a reasonable read-only picture, but there is no mention of error behavior (unknown ID), permissions, or how complete/heavy the payload is.

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?

Two short sentences, no filler; the key disambiguator (Radarr ID) and the return-content summary are both front-loaded and each sentence earns its place.

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?

There is no output schema, and the description partially compensates by naming the main payload sections (file info, ratings, collection data). For a one-parameter read tool this is close to sufficient, though return shape and failure modes remain unspecified.

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 100%, so the single parameter is already fully documented, including the 'not TMDB ID' distinction. The description merely restates 'by its Radarr ID' and adds no format, range, or lookup semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource (get a movie) plus the lookup key (Radarr ID), which implicitly separates it from the sibling radarr_get_movie_by_tmdb and from radarr_get_all_movies. An agent can pick the right tool without opening the schema.

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?

Usage is implied by 'by its Radarr ID' plus the required id parameter, but there is no explicit when-to-use statement, no mention of when to prefer radarr_get_movie_by_tmdb or radarr_search_movies, and no exclusions or prerequisites.

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