Get TMDB Reviews

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

No annotations are provided, so the description is the only source. It discloses that results are paginated and that the operation is a 'gets' (read) action. However, it does not describe response structure, authentication requirements, or other limitations beyond pagination.

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?

The description is a single concise sentence that front-loads the verb and object. It contains no filler or redundancy.

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?

The tool has 4 parameters and no output schema, and the description is brief. It covers the core purpose but leaves out details about return fields and the meaning of the language parameter. For a simple retrieval tool, this is minimally sufficient but not rich.

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%, so the description is essential for parameter understanding. It implicitly explains mediaType (movie/tv) and page (paginated), but the language parameter is not mentioned, and id is only implied. The description adds some semantic context but not complete coverage.

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 gets paginated user reviews for a movie or TV series. It uses a specific verb and resource, and the scope distinguishes it from sibling tools like tmdb_get_movie or tmdb_get_credits.

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?

The description implies usage for retrieving reviews when you have a media type and ID, but it does not explicitly mention alternatives or conditions for when not to use it. The scope is clear but no comparative guidance is given.

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