Search Rotten Tomatoes movies and return normalized search rows from credential-free server-rendered HTML.
Rotten Tomatoes movie search. Returns normalized Rotten Tomatoes movie search rows from credential-free server-rendered search HTML.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Rows to return, default 10, max 20 | |
| query | Yes | Search query |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that results are normalized and come from credential-free server-rendered HTML, which provides insight into data source and auth requirements. However, no mention of rate limits, pagination behavior, or potential performance implications.
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?
Two sentences, directly addresses purpose and key characteristics. No extraneous information. Front-loaded with primary function.
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?
Adequate for a simple search tool with no output schema. Describes return type (normalized rows) and key aspect (credential-free). Could optionally mention the return format or fields, but not essential given low complexity.
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?
Input schema already provides descriptions for both parameters (query and limit) with 100% coverage. The description adds no additional semantics beyond what the schema offers.
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?
Clearly states it is a Rotten Tomatoes movie search tool, specifying it returns normalized search rows from credential-free server-rendered search HTML. Distinguishes from sibling tools like rottentomatoes_browse_movies and rottentomatoes_movie.
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?
Implied usage for searching movies on Rotten Tomatoes, but no explicit guidance on when to use this over other search tools or alternatives. No exclusions or conditions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.