tmdb_movie_list

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

No annotations are provided, so the description must carry full transparency burden. It discloses that the data is credential-free and public, indicating a safe read operation. However, it does not explain pagination behavior, result size limits, or the shape of returned data, which are important for an agent to form expectations beyond the minimal 'returns a chart' statement.

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 main action. The second sentence redundantly restates 'Returns a TMDB movie chart,' which is a minor flaw. However, the overall structure is efficient, and the 'Credential-free public TMDB data' sentence adds useful context without unnecessary verbosity.

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 14 optional parameters and no output schema, the description is too sparse. It does not mention the extensive filtering capabilities (date ranges, ratings, runtime, genres) or the structure of the returned movie list. This is a significant gap for a tool with this complexity; the agent would need to rely entirely on the schema to understand the tool's full capabilities.

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 provides 100% coverage for all 14 parameters, so the baseline is 3. The description adds value by explicitly listing the valid category values (popular, top rated, now playing, upcoming) that map to the 'category' parameter, which the schema does not enumerate. This extra detail helps the agent determine valid inputs.

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 tool's function with a specific verb ('Get'), a clear resource ('TMDB movie chart'), and enumerates the chart categories (popular, top rated, now playing, or upcoming). This distinguishes it from sibling tools like tmdb_search (movie search) and tmdb_tv_list (TV charts), making its purpose unmistakable.

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 usage for fetching predefined movie charts but does not explicitly state when to use this tool versus alternatives such as tmdb_search or tmdb_movie. It mentions 'Credential-free public TMDB data,' which gives some context about no-auth access, but it lacks explicit when-to-use or when-not-to-use guidance.

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