rottentomatoes_editorial_content

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

No annotations are provided, so the description carries the burden. It discloses that results are paginated and that content is 'public' (no auth implied), and that 'pages' acts as a special index collection rather than content. It says nothing about rate limits, error behavior, or what a record contains, so the behavioral picture is only partial.

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 sentences, all front-loaded, ending with the actionable routing hint. Slight redundancy between 'Rotten Tomatoes editorial content listing' and 'Lists paginated editorial records', but no sentence is wasted.

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?

For an 8-parameter, enum-heavy listing tool with no output schema, the description covers the core operation and the type-discovery path but omits what a returned record contains and how taxonomy/query/operator filters combine. Adequate but with visible gaps for a tool of this complexity.

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 100% and three parameters have enums, so the schema already documents every field thoroughly. The description adds only the cross-reference for discovering valid 'type' values and the 'pages' collection semantic, which is genuinely useful but marginal against a fully documented schema. Baseline 3 applies.

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 and resource: 'Lists paginated editorial records from the selected public content type.' An agent understands this is a filtered listing tool keyed on the required 'type' parameter, and the mention of the 'pages' collection adds a distinct behavior. However, it never differentiates itself from the close sibling rottentomatoes_editorial_search, so the agent must infer which listing to pick.

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?

Gives one actionable routing hint – 'Use the editorial types endpoint to discover accepted type values' – which correctly points at rottentomatoes_editorial_types. But it offers no guidance on when to choose this listing over rottentomatoes_editorial_search or editorial_detail, leaving the primary selection decision implicit.

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