Search TMDB Movies

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

No annotations are provided, so the description carries the full burden. It adds one behavioral detail—that matching occurs across multiple title types—but does not disclose whether the operation is read-only, how results are paginated, or any other side effects. This is insufficient for a safe and predictable usage.

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, focused sentence that is front-loaded and contains no filler. It effectively communicates the core purpose without any waste.

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 has 6 parameters, no annotations, and no output schema. The description is too brief to cover essential context such as the response format, pagination behavior, or how the optional filters (year, region, language) affect results. It is incomplete for a tool with this complexity.

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?

The schema has zero descriptions for all 6 parameters. The description only clarifies the 'query' parameter by specifying it matches original, translated, and alternative titles. It provides no meaning for 'page', 'year', 'region', 'language', or 'includeAdult'.

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 clearly states the action ('searches'), the resource ('movies'), and the specific scope ('by original, translated, and alternative titles'). This distinguishes it from sibling tools like tmdb_search_tv or tmdb_search_collections.

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 implies when to use the tool (when searching for movies by title) but does not explicitly mention alternatives or exclusions. There is no guidance on when to use tmdb_discover_movies versus this search tool.

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