radarr_lookup_movie

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

The only annotation is readOnlyHint=true, which already conveys that the operation is safe and non-destructive. The description adds no additional behavioral context such as whether the lookup returns a list of matches, how matches are ordered, or any rate limits. It fails to explain the core behavior beyond the annotation.

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 short but under-specified. It includes only a redundant phrase ('List lookup') and a restatement of the schema. Good conciseness would convey the necessary information in a minimal but meaningful way; this does neither.

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?

Although an output schema exists, the description is too sparse to provide a complete picture of the tool's purpose and behavior. It does not explain that this tool searches for movies by term, what the response contains, or how it differs from other lookup endpoints. The description fails to fulfill even the basic requirement of telling the agent what the tool does.

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 a single parameter 'term' with 0% description coverage. The description merely repeats 'Query params: term' without explaining that 'term' is a search query string for movie titles or how it should be formatted. The agent gains no additional meaning beyond the parameter name.

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 'List lookup' is extremely vague and essentially repeats the tool name without specifying what is being listed or what a lookup entails. It does not distinguish this from sibling tools like lookup_movie_by_imdb_id or lookup_movie_by_tmdb_id, nor does it mention that 'term' is used to search for movies by title.

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?

There is no guidance on when to use this tool versus the alternative lookup tools (by IMDb or TMDB ID). The description does not state any context, prerequisites, or exclusions, leaving the agent to guess which lookup is appropriate.

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