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. The description adds the cross-field applicability constraints on `parent` and `offset`, which is genuinely useful, but it duplicates what the schema descriptions already state rather than disclosing new behavior like pagination limits or return shape.

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 tightly written sentences with no filler, front-loading the core purpose before the sibling routing and parameter caveats. Efficient, though the parent/offset sentence slightly overlaps schema content.

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 a read-only list tool with a 100%-covered schema, existing annotations, and an output schema, the description covers purpose, routing, and key constraints. Return values need not be explained given the output schema; only minor pagination/behavioral detail is absent.

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%, so all 13 parameters are already documented in the schema (including the categories-only `parent` and offset-except-categories notes). The description restates those constraints rather than adding syntax, defaults, or format detail beyond the 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 (List) and resource (paginated Rotten Tomatoes editorial taxonomy-term records) with scope (search/order/assignment filters). It names the two sibling tools it is distinct from (rottentomatoes_editorial_taxonomies, rottentomatoes_editorial_search), so an agent can route between them without opening schemas.

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?

Explicitly routes the agent: discover taxonomy names via rottentomatoes_editorial_taxonomies and use rottentomatoes_editorial_search for content search. It also flags applicability of `parent` and `offset`. Lacks an explicit when-not-to-use statement for this tool itself, hence not a 5.

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