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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavioral context beyond them: the source is a 'credential-free public series page' and the output is 'normalized,' which tells the agent no auth is required and the payload is standardized. It stops short of noting rate limits or failure modes.

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 short, front-loaded sentences with no filler: purpose, parameter rule, then alternative routing. Efficient overall, with only the minor 'rotten Tomatoes' casing slip as a blemish.

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-value detail is not required. For a two-param, read-only tool the description covers purpose, the auth-free source, the mutual-exclusion rule, and the sibling alternative. The only gap is not addressing the season/episode siblings an agent might confuse it with.

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 100%, so the baseline is 3, but the description adds a constraint the schema does not express: 'Pass exactly one of path or url.' Since there are two optional params and no oneOf, this mutual-exclusivity rule is real added value over the structured field definitions.

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+resource ('Returns normalized Rotten Tomatoes TV series metadata and scorecard data') and explicitly names the sibling rottentomatoes_movie as the different resource. It does not distinguish itself from the other closely related TV tools (rottentomatoes_season, rottentomatoes_episode), but the core purpose is unambiguous.

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?

'Use rottentomatoes_movie to retrieve movie detail' gives one explicit alternative and its selecting condition. However, there is no when-to-use guidance relative to the more closely competing TV/season/episode siblings, and the 'Pass exactly one of path or url' line is parameter guidance rather than selection guidance.

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