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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world behavior are covered structurally. The description adds that results are searchable and paginated, which is useful behavioral context, but it doesn't explain what "discovered content type" means or where the valid type values come from (e.g., rottentomatoes_editorial_types).

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?

A single, front-loaded sentence with no filler. It is efficiently sized, though the brevity comes partly at the cost of substance rather than through tight editing of redundant 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?

An output schema exists, so return values need not be described. But for an 8-parameter tool with 0% schema coverage and several unexplained params (taxonomy, term_ids, operator, include_children), the one-line description is too thin to call the tool confidently, and the required "type" param's valid values are never sourced.

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 0% across 8 parameters, so the description must carry the load. It only loosely gestures at three of them (type via "content type", query via "search", page/limit via "pagination") and says nothing about operator, taxonomy, term_ids, or include_children, leaving half the surface undocumented in both places.

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 states a verb ("List") and a resource ("Rotten Tomatoes editorial records") plus a scoping dimension ("by discovered content type"). However, "discovered content type" is opaque phrasing and the description does nothing to separate this tool from close siblings like rottentomatoes_editorial_search, rottentomatoes_editorial_detail, or rottentomatoes_editorial_types. Purpose is inferable but not sharply defined.

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 when-to-use guidance and no mention of alternatives, despite several overlapping editorial siblings (editorial_search, editorial_detail, editorial_section, editorial_types). The agent is left to guess whether this is a browse endpoint, a search endpoint, or both.

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