list_movie_lookup_imdb

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the HTTP method and endpoint path, which is minor but useful context. It does not disclose any additional behavioral traits such as rate limits, required authentication, or error behavior, but the annotations carry most of the burden here.

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 very short and front-loads the core statement 'Read MovieLookup' followed by the endpoint. It wastes no words, though it is arguably too terse to be fully useful. The structure is clean and scannable.

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 lookup tool with one optional parameter and an output schema, the description is minimal but not entirely inadequate. However, it fails to explain what the lookup returns, how the imdb_id should be formatted, or how this differs from the TMDB lookup sibling. An agent would need to infer too much from the endpoint path alone.

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 undocumented parameter. The description only lists 'imdb_id: Query parameter' with no format, example, or explanation of what values are valid. The schema shows it is a nullable string with a default of null, but the description adds no meaning beyond that.

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 says 'Read MovieLookup' and includes the endpoint 'GET /api/v3/movie/lookup/imdb', which identifies the resource and operation. However, it does not explain what a MovieLookup is or what the returned data represents, and it does not distinguish this from the sibling list_movie_lookup_tmdb beyond the endpoint name.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for IMDb ID lookups specifically, nor does it contrast with list_movie_lookup_tmdb or list_movie_lookup. The endpoint path implies the use case, but the description itself offers no explicit usage context.

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