search_imdb

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

No annotations are provided. The description lists returned fields (ratings, year, cast, IMDb links) and that it searches movies and TV shows, but omits details on error handling, partial matching, or result limits beyond the schema.

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?

Two sentences convey the essential information without waste. The structure is front-loaded with the action and resource, then details modes and outputs.

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 simple search tool with three optional parameters and no output schema, the description adequately covers inputs and outputs. Missing behavioral details (e.g., error handling) but still sufficient for an agent to select and invoke the tool correctly in most cases.

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%, but the description adds value by naming charts in plain English (e.g., 'Top 250 Movies' for 'top' enum) and clarifying that query is for title search. This provides meaning beyond the schema field 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 clearly states 'Search IMDb for movies and TV shows', using a specific verb and resource. It distinguishes from sibling tools (e.g., search_houzz) by being IMDb-specific.

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 notes two modes: search by title or browse curated charts. It provides context for use but does not explicitly state when not to use or alternatives. However, sibling tools are all different domains, so the context is clear.

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