imdb_title

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

Mentions 'credential-free public' source, indicating no auth required. But no disclosure of rate limits, error handling, or data freshness. With no annotations, more detail would be beneficial.

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?

Extremely concise at two sentences. No redundant information, front-loaded with purpose. Every 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?

No output schema provided, and the description gives no indication of what fields are returned (e.g., title, year, rating). This lack of return value context limits the agent's ability to use the tool effectively.

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 already provides descriptions for both parameters (100% coverage). The description adds the critical constraint 'exactly one of id or url', which is not in the schema and enhances understanding.

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 it returns 'normalized IMDb title metadata', specifying the resource and action. It distinguishes from sibling search tools but does not explicitly differentiate from other title-specific tools like imdb_title_credits.

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?

Provides explicit instruction to pass exactly one of id or url, which is helpful. However, it lacks guidance on when to use this tool versus alternatives like imdb_title_awards or imdb_search.

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