rottentomatoes_episode

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

Discloses that the tool accesses a 'credential-free public episode page', implying no authentication needed. Lists the types of data returned. No annotations provided, so description carries burden; it covers read-only behavior but omits details like rate limits or error scenarios.

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?

Two concise sentences: first describes the tool's output, second provides parameter guidance. No fluff, front-loaded with key information.

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 purpose, output, and parameter usage. Lacks specifics on path format (e.g., relative vs absolute) and prerequisites, but overall sufficient for a simple two-parameter tool with high schema coverage.

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?

Adds significant value beyond the input schema by specifying the 'exactly one' constraint and the absolute URL format. Schema coverage is 100%, but the description clarifies usage condition that the schema alone does not enforce.

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 'Rotten Tomatoes TV episode metadata, scorecard data, parent series/season metadata, and public video metadata'. Distinguishes from sibling tools like rottentomatoes_season and rottentomatoes_series by focusing on the episode level.

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?

Provides explicit instruction to pass exactly one of `path` or `url`, and specifies the URL must be absolute from rottentomatoes.com. However, does not explicitly mention when to use this tool versus siblings (e.g., rottentomatoes_season for season-level data).

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