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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world behavior are covered. The description adds nothing beyond that: it says nothing about pagination, row structure, filtering behavior, or how the many filter parameters interact, which for a discovery/browse endpoint is a notable gap.

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?

It is short, but the brevity comes from under-specification rather than economy - a single noun phrase with no verb and no front-loaded statement of purpose. There is no wasted wording, but there is also no useful wording.

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?

An output schema exists so return values need not be described, but that is the only burden lifted. For a 9-parameter browse endpoint with no required params and no schema descriptions, the description should orient the agent to what the rows are, how filtering works, and how to choose the tool; it does none of this.

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?

Nine parameters (list, sort, after, limit, genres, critics, ratings, audience, affiliates) have 0% schema description coverage and no enums, and the description explains none of them - not even the role of 'list' or the pagination cursor 'after'. With zero compensation for a total coverage gap, this is maximally deficient.

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 fragment 'Rotten Tomatoes TV discovery rows' names a source and a resource ('TV discovery rows') but supplies no verb, so it is essentially a paraphrase of the tool name rather than a statement of what the tool does. It hints at the TV-vs-movies split with its sibling rottentomatoes_browse_movies, but an agent still cannot tell what action is performed.

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 or when-not-to-use guidance and no mention of alternatives such as rottentomatoes_browse_movies, rottentomatoes_browse_filters, rottentomatoes_search, or rottentomatoes_series. The TV scope is only implied by the word 'TV', leaving the agent to guess which browse-family tool to pick.

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