list_movie_lookup_tmdb

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 only the endpoint path and arg name, and 'Read MovieLookup' without explaining behavior — e.g., that this queries an external TMDB service or that an unmatched ID yields an empty result. No behavioral context beyond the annotations is provided.

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 compact and cleanly structured around endpoint and args. But the brevity is under-specification rather than disciplined conciseness — it omits the core purpose. Front-loading 'Read MovieLookup' gives the agent no actionable summary.

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?

The tool is simple (one optional parameter) and an output schema exists, which covers the return shape. But the description omits the core purpose, the distinction from sibling lookup endpoints, and any behavioral context. For a tool whose name prominently includes a source (tmdb), the description should state what it returns and when to prefer it.

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 carries the burden of documenting tmdb_id, but it only repeats the parameter name and labels it a query parameter. There's no explanation that tmdb_id is the external TMDB identifier used to fetch the movie record. The parameter name is self-hinting but the description adds minimal semantic value.

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 provides a verb ('Read') and a resource ('MovieLookup'), and spells out the endpoint path which identifies the TMDB lookup scope. However, it never states what the tool actually does — fetch movie metadata from TMDb for a given ID — and doesn't distinguish it from sibling tools list_movie_lookup and list_movie_lookup_imdb. The name and endpoint do most of the clarifying work.

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 about when to call this tool. It does not mention siblings list_movie_lookup or list_movie_lookup_imdb, nor the conditions that would favor this endpoint over those. An agent is left to infer the use case entirely from the tool name.

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