rottentomatoes_browse_movies

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

No annotations are provided, and the description only mentions 'credential-free JSON-LD ItemList data' without disclosing rate limits, pagination behavior, or whether results are cached. More transparency is needed for a read-only browsing tool.

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?

Concise, no filler sentences; front-loaded with purpose, then enumerates parameters efficiently.

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?

Adequately covers tool purpose and parameter usage, but could improve by indicating the output structure (e.g., fields in 'normalized movie rows') since no output schema exists.

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?

Description adds significant value beyond the input schema by enumerating valid enum-like values for list and sort and specifying constraints, even though schema descriptions are present.

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 the tool returns normalized movie rows from Rotten Tomatoes public browse pages, distinguishing it from other Rotten Tomatoes tools like search or individual movie details.

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?

Explicitly lists supported list and sort values with their constraints (e.g., 'top_box_office' only valid with 'movies_in_theaters'), but does not provide when-to-use versus sibling tools beyond implicit browsing context.

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