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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known without the description. The description adds nothing further - no note on what identifies the title, whether results are paginated, or how locations are structured.

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?

It is a single short sentence, but brevity here reflects under-specification rather than conciseness. There is no front-loaded verb or scoping detail to anchor the call.

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?

An output schema exists, so return values need not be described, but with two undocumented parameters, no usage guidance, and no behavioural context, the definition is not sufficient to call the tool correctly without external assumptions.

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?

Both parameters (id, url) have 0% schema description coverage and the description says nothing about them. It does not clarify the id format (e.g. tt-prefixed IMDb id) or the relationship/precedence between id and url, so an agent must guess.

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 phrase 'IMDb title filming locations' restates the tool name almost verbatim and names no verb or scope. An agent learns only that it concerns filming locations of a title, which the name already conveys.

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?

There is no indication of when to call this instead of imdb_title, imdb_title_release_info, or any other title-related sibling, and no prerequisites are stated. The description gives zero routing guidance.

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