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 about behavior — not review source (critics vs. audience), pagination via 'after'/'limit', or what the url/path/type inputs address, leaving the agent with only the annotations to rely on.

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 single fragment is short but does not earn its place because it conveys almost no actionable information. Brevity here reflects under-specification, not efficient structure.

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?

For a 5-parameter tool with zero schema coverage, the description is completely inadequate. Although an output schema exists (so return values need not be explained), nothing about input usage, review scope, or filtering is provided.

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?

All 5 parameters (url, path, type, after, limit) have 0% schema description coverage, and the description supplies none of the missing meaning. The semantics of 'type', 'path', and 'url' versus 'after'/'limit' are entirely undocumented anywhere.

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 merely restates the tool name ('Rotten Tomatoes movie reviews') without a verb or action, so the agent cannot tell whether it lists, searches, or fetches reviews. It loosely signals the resource (movie reviews) versus siblings like rottentomatoes_movie or rottentomatoes_search, but provides no distinguishing scope such as critic vs. audience reviews.

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?

There is no when-to-use, when-not-to-use, or alternative guidance at all. With many nearby siblings (rottentomatoes_movie, rottentomatoes_search, rottentomatoes_critics_authors, rottentomatoes_series), the agent is left to guess which tool returns review data.

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