OMDb — Search

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not state whether this is read-only, requires an API key, has rate limits, returns partial matches vs exact matches, or what the result structure looks like. For a search tool with no annotation coverage, this is a meaningful 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 with zero waste. However, brevity here borders on under-specification rather than efficiency — while it's concisely written, it leaves substantial information absent.

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 generic search endpoint with 4 parameters, no output schema, and no annotations, the description is thin. It doesn't clarify the fuzzy-match behavior, pagination semantics for the page parameter, or how results are ordered/scored, which are important for an agent deciding how to use a search tool.

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 for the 4 parameters. It mentions title/year/type broadly but adds no detail beyond what the schema property names already convey. It omits 'page' entirely and provides no guidance on format constraints (e.g., year as 4-digit, type enum values).

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 'Search OMDb by title/year/type' which is a specific verb+resource with the key search dimensions. However, it does not differentiate from sibling search tools like film_tmdb_search_movie or books_openlibrary_search, and the generic 'Search' doesn't clarify what result set or filtering behavior this returns.

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 vs the sibling film_tmdb_search_movie, film_omdb_get, or the cross-across-all search tools. The description provides no exclusions or alternative tool recommendations, leaving the agent to guess when a TMDB search vs OMDb search is appropriate.

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