list_movie_lookup

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description only adds 'Read' and the GET endpoint, which largely repeats the annotations rather than disclosing additional operational behavior such as result scope, filtering semantics, or side effects.

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 and front-loaded with the action and endpoint, followed by the argument list. Minor redundancy exists between 'Read MovieLookup' and the GET endpoint, but overall the structure is efficient.

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?

Although the output schema exists and annotations cover read-only/idempotent behavior, the description is incomplete for agent decision-making. It does not explain what the lookup actually does, what 'term' should contain, or how it differs from the IMDb/TMDB-specific lookup siblings.

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 'term' parameter. It only says 'term: Query parameter', which describes the transport location but not the meaning, allowed values, or expected format of the term.

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 a clear verb ('Read') and identifies the resource ('MovieLookup') with the endpoint 'GET /api/v3/movie/lookup'. It does not, however, distinguish this from sibling tools like list_movie_lookup_imdb or list_movie_lookup_tmdb, so it stops short of full clarity.

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 usage guidance is provided. There is no statement about when to use this lookup instead of alternatives such as list_movie_lookup_imdb, list_movie_lookup_tmdb, or list_movie, and no mention of preconditions or context.

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