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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile (public, non-destructive read) is covered by structured data. The description adds only 'normalized rows', hinting that output is standardized across charts, but says nothing about pagination behavior, rate limits, or which chart values are valid for a mutation-free lookup.

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 redundancy. It is efficient, but the brevity is partly under-specification rather than disciplined economy.

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 shape need not be spelled out. But for a two-parameter tool with 0% schema coverage, the description omits the one thing an agent cannot infer: which chart identifiers are accepted and any limit default or ceiling, making the definition insufficient to call correctly.

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 neither parameter is documented in the schema; the description likewise says nothing about valid 'chart' values or what 'limit' bounds. This is the most dangerous gap, since 'chart' is a free-form string with no enum, leaving the agent unable to construct a valid call without trial and error.

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?

States a specific verb ('Returns') and resource ('public IMDb title charts'), so an agent can tell it retrieves chart data rather than searching titles or fetching a single title's details. However, 'normalized rows' is vague about what is actually returned and which charts exist, so it stops short of a fully disambiguating 5.

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 or imdb_title, nor any context about which scenarios call for chart data. The agent gets no exclusions, prerequisites, or routing guidance.

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