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 covered. The description adds genuinely useful context beyond them: no credentials are required and results are normalized rows scraped from public IMDb pages, implying possible rate limits or staleness. It stops short of disclosing pagination behavior or what the row normalization entails.

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?

A single front-loaded sentence with no filler or repetition. It is efficiently sized, though the brevity is partly a consequence of omitted information rather than disciplined trimming.

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 no explanation. But for a 2-parameter search tool with 0% schema coverage and a confusingly similar sibling, the definition leaves real gaps: the limit parameter and the distinction from imdb_search_title are both unaddressed.

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% and the description never mentions either parameter. 'title search rows' weakly implies that query is a title term, but the 'limit' parameter is completely undocumented in both schema and description, leaving its meaning, default, and maximum unknown.

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 sentence names a verb (search) and resource (IMDb titles) and hints at the output shape (normalized rows). However, it does not distinguish this tool from the near-identical sibling imdb_search_title, which by name appears to be the canonical title search. An agent seeing both cannot tell from this text which one to pick.

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 statement of when to use this versus imdb_search_title, imdb_title, or imdb_charts, no mention of prerequisites, and no guidance on how the result set is bounded. The only contextual clue ('credential-free public pages') is a data-source remark, not usage guidance.

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