tmdb_movie_reviews

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

With no annotations, the description carries the responsibility of disclosing behavior. It states the return format ('Formatted string with movie reviews') and default parameter behaviors, but does not mention potential errors, pagination behavior beyond the page parameter, or any rate-limits. The tool is a simple read operation, so the provided info is adequate but not rich.

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 two sentences with a clear purpose, followed by a concise, well-structured Args list. Every element adds value: the purpose, the three parameters with defaults, and the return format. No unnecessary words or repetition.

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 covers the essential aspects: what it does, the parameters, and the return value. An output schema exists, so detailed return structure is not required here. The description is complete enough for a straightforward retrieval tool.

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?

The schema has no parameter descriptions (0% coverage), but the description compensates fully by explaining each parameter: movie_id as TMDB ID, language as language code with default en-US, and page as result page with default 1. This adds meaning beyond the raw schema types and defaults.

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 'Get the user reviews for a movie from TMDB', using a specific verb and resource. It distinguishes from siblings like tmdb_tv_reviews by specifying 'movie' and from tmdb_review_details by focusing on all reviews rather than a specific review.

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 clearly implies when to use this tool: when user reviews for a movie are needed. It does not explicitly exclude alternatives like tmdb_tv_reviews, but the resource specification makes it obvious. Default parameter values are provided, offering implicit guidance on typical usage.

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