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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds pagination behavior (map next_cursor to after / previous_cursor to before) and the notion of current-vs-inactive critics, but much of this restates the schema's own cursor and inactive field descriptions rather than adding new 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?

Purpose is front-loaded and the total length is reasonable with no filler. The cursor-mapping sentence sits awkwardly between the mode description and the limit note, and it re-explains schema detail, but overall the structure is efficient.

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?

With an output schema present, return values need not be described, and annotations cover safety. The description covers both access modes, pagination, and the cross-reference to rottentomatoes_person, leaving little an agent needs beyond the (fully documented) schema.

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 coverage is 100%, so the schema already documents all six parameters including defaults, ranges, and mutual exclusivity. The description's limit and letter remarks largely repeat the schema, so the baseline of 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 (Returns) and resource (current or inactive critics from Rotten Tomatoes' public author directory), and distinguishes the two access modes (browse one letter vs. search by name). It also names a sibling it is not (rottentomatoes_person), so an agent can separate it from the detail tool without opening the schema.

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: use this to browse a letter or search by name, and use rottentomatoes_person for person detail and filmography. That is a clear when-to-use and an alternative, though it stops short of stating any when-not-to-use or prerequisite conditions.

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