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 that both active and inactive critics are returned, which is useful context, but says nothing about pagination (after/before/limit) or result ordering.

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?

A single compact sentence with no filler and no wasted words. It is front-loaded, though its brevity borders on under-specification rather than tight efficiency.

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 6-parameter filtering/browsing tool with 0% schema description coverage, a single fragment is not enough. An output schema exists so return values need not be described, but the filtering parameters and their interactions are left undocumented.

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% across 6 parameters, and the description compensates almost nothing. The only hint is that 'inactive' is included, vaguely relating to the inactive param; ambiguous params like 'letter', 'after', and 'before' remain entirely unexplained.

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 names a specific resource (a critics/author directory) and adds scope the tool name lacks by noting it covers 'current and inactive' critics. It lacks an explicit verb and does not distinguish itself from siblings like rottentomatoes_person or rottentomatoes_movie_reviews, but an agent can tell it is a listing of critics.

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 guidance, no prerequisites, and no named alternative among the many Rotten Tomatoes siblings. The agent must infer the tool's role purely from the noun phrase.

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