radarr_get_movie

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

The readOnlyHint annotation already establishes this as a safe read operation. The description adds the ID-based lookup context but doesn't disclose any other behavioral traits (e.g., error handling, response format). It does not contradict annotations.

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 very concise and front-loaded, but contains a typo ('movies' instead of 'movie'). It earns an efficient single sentence with no waste, though the error slightly reduces polish.

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's simplicity (one parameter, clear purpose) and the presence of an output schema, the description is largely complete. It lacks explicit usage guidance relative to siblings, but for a straightforward fetch-by-id operation, it provides sufficient context.

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?

The schema has one required integer 'id' with 0% description coverage. However, the description compensates by explicitly saying 'by id', clearly indicating the parameter's purpose. Since the parameter name is self-explanatory and the description reinforces it, this is adequate.

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 'Fetch a single movies by id' with a specific verb and resource, and it distinguishes itself from sibling tools like radarr_list_movie by specifying retrieval of one movie by ID. Despite a minor grammar issue, the intent is unambiguous.

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 implies usage when a specific movie's details are needed by ID, but it does not explicitly contrast with alternatives like radarr_list_movie or other getters. No exclusions or when-not-to-use guidance is provided.

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