Search TMDB Keywords

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 mentions 'searches' which implies a read operation, but does not disclose pagination behavior, return format, or any side effects. The description adds minimal behavioral context beyond the tool's name and title.

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, concise sentence that efficiently conveys the core purpose. There is no redundant filler or repetition of structured data, making it appropriately sized for a simple search tool.

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 is simple with only two parameters and no output schema. The description provides enough context to understand the tool's purpose and intended use in discovery workflows, but lacks details on return structure and pagination. Given the simplicity, a moderate score is appropriate; it is not fully complete but not severely deficient.

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 description provides no information about the query or page parameters. Schema description coverage is 0%, so the description must compensate for the schema's minimal annotations. It does not explain what 'query' means or how to use 'page', leaving the agent without guidance beyond the raw schema.

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: it searches for keyword IDs intended for movie and TV discovery. This is a specific verb+resource pattern that distinguishes it from sibling search tools like tmdb_search_movies or tmdb_search_people, which search for different entity types.

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 does not provide any guidance on when to use this tool versus alternatives, such as tmdb_search_movies or tmdb_discover_movies. It only states what it does, leaving the agent to infer usage context without explicit when-to-use or exclusion criteria.

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