radarr_lookup_movie_by_tmdb_id

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

readOnlyHint=true indicates read-only, and 'List' aligns with a read, but description adds no context about behavior, return format, or exact-match semantics. 'search term' is misleading for an ID lookup.

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's not conciseness but lack of substance. It reads like an incomplete stub.

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?

For a one-parameter read-only lookup with an output schema, the description still needs to state exact-ID lookup and relationship to sibling lookup tools. It provides almost no useful 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?

Schema coverage is 0%, so description should explain tmdb_id. It merely restates 'tmdb_id' as a query param and incorrectly frames it as a search term rather than an exact identifier.

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 says 'List tmdb matching a search term' but the tool looks up a movie by exact TMDB ID; 'search term' is inaccurate. It doesn't mention 'movie' or 'lookup by ID', nor distinguish from sibling lookup tools.

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 on when to use this vs radarr_lookup_movie or radarr_lookup_movie_by_imdb_id. The only implied usage is a non-existent search term, which is misleading.

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