imdb_title_images

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It discloses output content (image metadata fields), the effect of omitting `type` (returns every type), default and maximum `limit` values, and the mutual exclusivity of `id` and `url`. For a read-only retrieval tool, these are important behavioral traits. It does not mention pagination beyond limit, error conditions, or rate limits, which would be nice but are not critical for a simple image-metadata endpoint.

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 approximately 70 words, front-loaded with the tool's purpose, then efficiently covers filters, defaults, and parameter constraints. Every sentence contributes necessary information: purpose, returned fields, filter semantics, limit behavior, and the id/url exclusivity. There is no filler or redundancy, making it highly concise and well-structured.

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?

For a tool with 4 optional parameters, no output schema, and no annotations, the description is fairly complete. It explains what the tool returns, the key fields, the filter options, and the required input constraint. It does not detail the full output structure (e.g., list/object, pagination tokens), but for a simple image-metadata endpoint the provided information is sufficient for an agent to invoke it correctly. Missing output schema details could be a minor gap, but not a significant one.

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 coverage is 100%, so the baseline is 3. The description adds meaningful cross-parameter semantics not present in the schema: the requirement to pass exactly one of `id` or `url` (a constraint invisible in the schema's `required: []` list). It also clarifies the effect of omitting `type` ('Omit `type` to return every type') and reiterates the limit behavior. This goes beyond simple repetition of schema descriptions.

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 states a specific verb and resource: 'Returns image metadata from a title's media index' for 'IMDb title images'. It clearly identifies the data scope (title images) and lists the fields returned (URL, dimensions, caption, credited people). While it doesn't explicitly contrast with sibling tools like imdb_name_images, the resource noun 'title' differentiates it sufficiently, though not as forcefully as naming the sibling.

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 provides operational guidance: how to filter by `type`, how `limit` works, and the exclusivity requirement 'Pass exactly one of `id` or `url`'. However, it does not explicitly state when to use this tool versus alternatives (e.g., imdb_name_images, imdb_title_videos). The usage context is implied by the purpose, but no exclusions or comparisons are offered. This meets the 'implied usage' level, not explicit guidance.

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