radarr_lookup_movie_by_imdb_id

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

Although the readOnlyHint annotation indicates a safe read operation, the description adds no additional behavioral context. It does not clarify what a successful lookup returns, whether it can return multiple results, or how the imdb_id should be formatted (e.g., 'tt1234567'). The description provides no value beyond the annotation for understanding the tool's runtime behavior.

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 only two sentences but is under-specified and poorly structured. The first sentence is confusing and the second merely restates the parameter. It gives no useful information in an efficient way; this is not conciseness but incompleteness.

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) and the presence of an output schema, the description should at least explain the purpose, the expected ID format, and what the response represents. The description leaves the agent guessing about the return value and the exact meaning of 'imdb'. It is not sufficient for correct tool selection or invocation.

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%, so the description must compensate. However, it only repeats the parameter name 'imdb_id' without adding any format, requiredness, or example. It does not even explain that this parameter expects a valid IMDb ID, leaving the agent without essential information for proper invocation.

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 says 'List imdb matching a search term' which is vague and misleading; the tool actually looks up a movie by a specific IMDb ID. 'imdb' is not a clear resource, and the behavior described does not match the tool name 'lookup_movie_by_imdb_id'. The action verb 'List' and phrase 'matching a search term' poorly represent a precise lookup-by-ID operation.

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?

No guidance is provided on when to use this tool versus its siblings radarr_lookup_movie or radarr_lookup_movie_by_tmdb_id. There is no mention of alternatives or exclusions. The description simply states the parameter, leaving the agent to infer the appropriate context.

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