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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds nothing further: no note on whether url or path is required, no rate-limit or auth context, no indication of what is fetched. With the lower bar set by annotations, a 2 reflects a description that contributes no behavioral context.

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 single sentence is short but earns nothing; it is under-specification rather than conciseness. No information is front-loaded because there is no information at all.

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 need not be described, but the two undocumented input parameters and the absence of any routing guidance leave the definition materially incomplete for 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 coverage is 0% for two parameters named url and path, and the description supplies no explanation of either. The critical ambiguity of which identifier to pass (and in what format) is undocumented in both schema and description.

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 episode detail" essentially restates the tool name, adding only the weak verb "detail." It does not distinguish this from sibling retrievers such as rottentomatoes_series, rottentomatoes_season, or rottentomatoes_movie, so an agent cannot tell from the text which resource is returned.

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 (rottentomatoes_series/season), and no prerequisites. The agent is left to infer everything from the tool name alone.

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