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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds nothing beyond that: it does not explain pagination via the "after" cursor, sorting behavior, or what a discovery row contains, so it fails to enrich the behavioral picture.

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 a single short sentence with no filler, but for a 9-parameter browse tool it is severely under-specified rather than genuinely concise. Brevity here comes at the cost of usability.

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?

Although an output schema exists (so return values need not be described), the tool exposes 9 fully undocumented parameters and gives no usage context. For a tool of this complexity, the description is completely inadequate.

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?

There are 9 parameters with 0% schema description coverage, yet the description mentions none of them. It offers no hint about what "list", "sort", "critics", "ratings", or "audience" mean or their accepted values, leaving every parameter undocumented.

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?

"Rotten Tomatoes movie discovery rows" essentially restates the tool name (browse_movies) without clarifying what a "discovery row" is or what the tool returns. It does not distinguish this from sibling tools like rottentomatoes_browse_tv or rottentomatoes_browse_filters, leaving the agent to guess at the actual verb and output shape.

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 contains no when-to-use guidance, no prerequisites, and no mention of alternatives such as rottentomatoes_search or rottentomatoes_browse_filters. An agent has no basis for choosing this tool over its many siblings.

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