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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the safety profile is covered elsewhere. The description adds no behavioral context at all – no note on how the resource is identified, whether url and path are interchangeable, or any rate/scope caveats.

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?

Three words are not wasteful in a literal sense, but this is under-specification masquerading as conciseness. Nothing is front-loaded because there is effectively no content to prioritize.

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 needn't be described, but the description still leaves an agent unable to determine what input to supply of the two undocumented, optional parameters. For a detail-fetch tool this is 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?

Schema description coverage is 0% and the description supplies nothing about the two parameters. It doesn't explain what url vs path means, which is required, or how they relate – for example whether one is a Rotten Tomatoes URL and the other a site-relative path.

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 detail" essentially restates the tool name (rottentomatoes_movie) with the word "detail" tacked on. It doesn't clarify what kind of detail is returned or how the movie is identified, and it gives no basis for distinguishing it from rottentomatoes_movie_reviews, rottentomatoes_search, or rottentomatoes_series.

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 guidance, no mention of alternatives, and no prerequisites. An agent has no signal for choosing this over rottentomatoes_movie_reviews or rottentomatoes_search for a movie-related query.

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