Search movies

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

Annotations provide readOnlyHint and openWorldHint, ensuring safety. The description adds that results include compact summaries, TMDB ID, and pagination info, which gives clear behavioral context beyond the annotations.

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?

One sentence conveys the core action, result format, and integration with other tools. No wasted words; front-loaded with the verb and resource.

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?

With 6 parameters, no output schema, and good annotations, the description covers the essential workflow (returns ID for other tools) and output structure. It does not detail parameter behaviors beyond the schema, but that is acceptable given schema coverage.

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 coverage is 100%, so the schema already documents all parameters. The description does not add new meaning to parameters (e.g., defaults, behavior), but it does summarize the overall result structure (compact summaries, pagination). This meets the baseline for high schema coverage.

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 it searches TMDB movies by title and returns compact summaries with TMDB ID and pagination info. It distinguishes from siblings like 'discover_movies' and 'search_tv' by focusing on title search and linking to other movie tools.

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 it (to get a TMDB ID for other movie tools) and what it returns (compact summaries, pagination). However, it does not explicitly state when not to use it versus alternatives like 'search_multi' or 'discover_movies', leaving some ambiguity.

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