Get IMDb/RT/Metacritic ratings

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

Annotations already mark it as read-only and open-world. The description adds useful context about relying on the OMDb API and requiring an API key, which supplements the annotations without contradiction.

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 sentences: first covers purpose and parameters, second provides usage guidance and prerequisite. No redundant text, effectively front-loaded with essential information.

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 read-only tool with three optional parameters and no output schema, the description sufficiently covers data source, identifier priority, and alternative tools. The output is implied (ratings from three sources), which is adequate given the lack of an output schema.

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 has 100% coverage with descriptions. The description adds value by stating imdb_id is preferred and takes precedence, and explains when title and year are used, going beyond the schema's basic descriptions.

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 clearly states it retrieves IMDb, Rotten Tomatoes, and Metacritic ratings from OMDb, with specific identifier options (imdb_id or title+year). It distinguishes itself from siblings like get_movie/get_tv by noting those already include ratings when a TMDB id is available.

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?

Explicitly advises preferring get_movie/get_tv when a TMDB id is available, and notes the prerequisite of OMDB_API_KEY. While it does not list all when-not cases, the guidance is clear and actionable.

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