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

Annotations already declare readOnlyHint=true and openWorldHint=true, lowering the bar, but the description adds nothing beyond them - no indication of what identifiers it accepts, whether it hits the live site, or any auth/pagination behavior. It 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?

It is a single short sentence, but this is under-specification rather than tight conciseness - the fragment carries almost no information and nothing is front-loaded beyond the resource name.

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?

Although an output schema exists (so return values need not be described), two undocumented input parameters plus no usage guidance leave the definition materially incomplete for even a simple detail-fetch tool.

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?

Both parameters (url, path) have 0% schema description coverage and neither is mentioned in the description, so an agent gets no guidance on the expected format or whether url and path are alternatives. The intuitive names hint at intent but the description does not compensate for the coverage gap.

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?

The description names the resource ('Rotten Tomatoes season detail') so an agent can tell it returns season-level data, distinguishing it loosely from rottentomatoes_series and rottentomatoes_episode. However it is essentially a restatement of the tool name plus 'detail', with no verb and no explicit differentiation from the many similar RT sibling tools.

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 statement of when to use this tool versus alternatives such as rottentomatoes_series, rottentomatoes_episode, or rottentomatoes_search. Usage can only be inferred from the resource name.

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