OMDb — Get by IMDb ID or title

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state what happens with ambiguous title/year lookups, what the response format contains, whether omitting all parameters returns an error, or any rate-limit considerations for the OMDb API. For a fetch tool, this is a notable gap.

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 a single short sentence, which is concise, but it is under-specified rather than efficiently specified. There is no front-loading of key decision information. It earns points for brevity but loses for substance.

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 fetch-by-identifier tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is insufficient. It doesn't explain return structure, the semantics of the plot parameter, which identifier takes precedence, or how to disambiguate results. A more capable description is warranted for this degree of ambiguity.

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, but it adds no parameter-level detail. It doesn't clarify how plot choices differ, whether title alone suffices or year is needed for disambiguation, or the relationship between title/year and imdbId. 4 parameters are entirely undocumented beyond their bare names.

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 states the verb 'Fetch' and the resource 'OMDb details', mentioning the lookup key (imdbId or title/year). It is somewhat clear but does not differentiate from the sibling tool film_omdb_search, which is also OMDb-related. The purpose is understandable but could more precisely state it retrieves a single record by identifier.

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 film_omdb_search, film_tmdb_get_movie, or others. It does not mention that imdbId is the preferred key vs title/year, nor exclusions like 'use title+year together for disambiguation'. No alternative tools are named.

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