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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds context about the returned content (author, rating, date, excerpt, link). It does not contradict annotations. It lacks pagination or sort details, but that is minor given the schema documents limit.

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 concise sentences with no filler. The purpose and key usage rule are front-loaded, and the sibling alternative is mentioned briefly. Every sentence earns its place.

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?

Given the tool's simplicity, the description is complete: it states the resource, the identifiers, the output fields, and the sibling alternative. Pagination behavior is covered by the schema's limit parameter, and annotations cover safety. Nothing critical 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 the description adds little parameter-specific meaning beyond what the schema already provides. The 'provide only one' rule is already embedded in the query parameter description. The description adds no extra semantics for the other parameters.

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 the tool returns user reviews for one movie or show, lists the specific fields (author, rating, date, excerpt, link), and distinguishes itself from movies_ratings by noting ratings alone live there. This gives an agent a precise, unambiguous purpose.

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 explicitly says to use for 'what do people say about X' questions and directs ratings-only queries to movies_ratings. It also instructs to provide only one of title, TMDB id, or IMDb id, which is essential for correct invocation.

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