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

Annotations already establish readOnlyHint=true and openWorldHint=true. The description usefully adds cursor pagination behavior and filter sourcing guidance, but it incorrectly states 'limit defaults to 10' while the schema says the default is 30, which could mislead an agent.

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 compact and front-loaded: purpose first, then filter sourcing, pagination, and sibling routing. Every sentence contributes to invoking the tool correctly.

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?

It covers purpose, filter sourcing, pagination, and the movie alternative, and the output schema exists so return values need not be explained. However, the contradictory limit default is a material gap for correct invocation.

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 100%, so the schema already documents all parameters including comma-separated filters and the 'after' cursor. The description mostly repeats that and introduces a conflicting limit default ('10' vs schema's '30'), adding incorrect rather than clarifying meaning.

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?

States a specific verb and resource: 'Browse Rotten Tomatoes TV series results with filters and cursor pagination.' It also explicitly distinguishes this tool from its movie counterpart by saying 'Use rottentomatoes_browse_movies for movies.'

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?

Gives explicit routing to auxiliary and sibling tools: 'Use rottentomatoes_browse_filters with list=tv_series_browse for current values' and 'Use rottentomatoes_browse_movies for movies.' It also explains pagination resumption with 'after' and the limit cap.

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