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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and scope profile is covered. The description adds that these are 'public' quote rows and that exactly one identifier must be supplied, but says nothing about pagination, result volume, or rate/auth behavior. Useful but thin beyond what the annotations and output schema already provide.

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, front-loaded with purpose, followed by the calling constraint and disambiguation routing. No filler or redundant restatement of the tool name.

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 to describe returns and annotations carry the safety profile, so the description only needs purpose, routing, and invocation constraints, all of which are present. Nothing an agent needs to call this correctly is missing.

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 both parameters are individually documented, giving a baseline of 3. The description adds value beyond the schema by specifying mutual exclusivity ('pass exactly one') and the expected id format (tt...), which the per-parameter schema text does not convey.

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 ('Fetch public IMDb dialogue quote rows for a title') and immediately distinguishes itself from the two nearest siblings, imdb_title_trivia and imdb_title_goofs. An agent can tell exactly what data comes back and how it differs from adjacent IMDb title tools.

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?

It names explicit alternatives and the conditions that select them: imdb_title_trivia for background facts, imdb_title_goofs for reported mistakes. The invocation constraint ('Pass exactly one title id or title URL') is also stated, so both routing and calling are covered.

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