Search TMDB Movie Collections

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'searches' and gives no detail about pagination, language handling, rate limits, or output structure. This leaves significant ambiguity about what the tool actually does when invoked.

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, front-loaded sentence with no filler, earning its place. However, the extreme brevity sacrifices explanatory value, making it concise but not optimally informative. It could be improved slightly without losing conciseness.

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?

Given there is no output schema and three parameters, the description omits critical context such as pagination behavior, language semantics, and what the results are used for (e.g., linking to tmdb_get_collection). An agent would need to guess or rely on external knowledge to use this tool correctly, so it is not contextually complete.

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 parameter documentation. It only clarifies the 'query' parameter as searching 'by name', while 'page' and 'language' are completely unexplained. This partial coverage is insufficient for a 3-parameter tool.

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), resource (movie franchises/collections), and method (by name). It effectively differentiates this tool from sibling search tools like tmdb_search_movies, tmdb_search_tv, and tmdb_search_people by targeting collections/franchises specifically.

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 finding collections/franchises by name but provides no explicit alternatives, exclusions, or when-to-use guidance. It relies on the resource name to convey context, which is sufficient for a basic understanding but not comprehensive.

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