Find TMDB Item by External ID

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

No annotations are provided, so the description carries the full burden. It merely states the action without disclosing any behavioral traits such as return format, potential multiple results, rate limits, or the need to specify an external source. This is a minimal restatement of the tool's purpose.

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 that is direct and front-loaded with the verb and resource types. It contains no fluff and each word adds value.

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?

Overall, the description is too sparse for a tool with no output schema and no annotations. It does not mention necessary details like the externalSource parameter, response structure, or any constraints. While the tool is simple, the lack of parameter context and behavioral caveats leaves meaningful gaps.

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. It does not explain any of the parameters. While the parameter names and the enum for externalSource are somewhat self-explanatory, the description adds no meaning about what externalId should contain or how language affects the result.

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 the specific verb 'Finds' and clearly enumerates the resource types (movies, TV series, seasons, episodes, or people). This distinguishes it from sibling tools that focus on search or retrieval by TMDB ID, making the 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 phrase 'from an external ID' clearly indicates the intended use case: when you have an external ID (e.g., IMDb ID) and want to find the corresponding TMDB item. However, it does not explicitly state when not to use it or mention alternatives, so it falls short of a 5.

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