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 nothing beyond that – no note on return format (e.g., language filtering, spoilers), data source, or response shape, despite the output schema existing.

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?

It is short and front-loaded, but the brevity is under-specification rather than economy: four words carry no actionable content for a tool with two undocumented parameters and a large ambiguous sibling set.

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?

With an output schema present the return format needn't be explained, but the description still omits identifier semantics and any disambiguation from siblings. For a 2-param tool in a dense imdb_title_* family, this is not sufficient to invoke it 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?

Two parameters (id, url) with 0% schema description coverage, and the description explains neither. It does not clarify whether id and url are alternatives, whether url takes an IMDb link, or which is preferred – the exact gap the description was supposed to fill.

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 'IMDb title quotes' essentially restates the tool name (imdb_title_quotes) with no verb and no scope. It hints at returning quotes from an IMDb title, but does not distinguish this from siblings like imdb_title_trivia, imdb_title_goofs, or imdb_title_reviews. This is close to tautology.

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?

No when-to-use guidance, no alternatives named, no exclusions. Given ~20 near-identical imdb_title_* siblings, an agent gets no help deciding when quotes is the right call versus trivia, goofs, keywords, or reviews.

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