Search TMDB Catalog

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and scope without revealing pagination behavior, language/adult filtering defaults, rate limits, or that it is a read-only operation. The description is too minimal to adequately disclose behavior.

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 sentence and is structurally clean, but it is under-specified for the tool's complexity. It does not provide enough information to be considered 'appropriately sized'—it sacrifices necessary detail for brevity.

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 four parameters, no output schema, no annotations, and a minimal one-line description. It lacks context about return values, parameter usage, pagination, or any operational behavior, making it severely incomplete for an agent to invoke correctly.

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%, and the description does not explain any of the four parameters (query, page, language, includeAdult). With no parameter documentation in either the schema or the description, the agent cannot infer parameter semantics beyond names/types.

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 uses a specific verb ('Searches') and clearly identifies the resource scope ('movies, TV series, and people in one request'). This distinguishes it from sibling tools like tmdb_search_movies, tmdb_search_tv, and tmdb_search_people by emphasizing the combined multi-type search.

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 phrase 'in one request' implies the tool is used when searching across multiple content types simultaneously, but it does not explicitly state when to prefer this over individual searches or mention any exclusions. No alternatives are named, so usage context is present but not fully elaborated.

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