rottentomatoes_movie_reviews

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

With no annotations provided, the description carries full burden for behavioral disclosure. It explains the tool returns reviews with pagination metadata from a public JSON source, but it does not mention rate limits, authentication requirements, or any potential restrictions on scraping. The term 'hydrated' implies some processing, but the behavior is adequately but not fully transparent.

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 three sentences long, with the first sentence stating the primary purpose. Every sentence adds essential information (what it returns, usage constraint, allowed types). No redundant or extraneous words.

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 absence of an output schema, the description should compensate by detailing the return structure. It mentions 'normalized critic or audience reviews including pagination metadata,' which is adequate but generic. It does not specify the format (e.g., a list of reviews with `page_info`), which would aid an AI agent in understanding the response shape.

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 schema already describes all parameters. The description adds value by explaining the mutual exclusivity of `path` and `url`, and by listing the allowed `type` values explicitly (which are not defined as enums in the schema). This provides clarity beyond what the schema alone offers.

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 it returns normalized critic or audience reviews from Rotten Tomatoes, with pagination metadata. It distinguishes itself from siblings like rottentomatoes_movie (which likely returns movie details) and rottentomatoes_search by specifying the resource (reviews) and source (review page JSON).

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 provides explicit guidance on how to use the tool: pass exactly one of `path` or `url`, and lists supported `type` values. It does not, however, compare directly with sibling tools or explain when to use this over alternatives like rottentomatoes_movie, which slightly reduces the score.

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