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 operational behavior beyond the annotations: cursor-based resumption via after from page_info.end_cursor and the limit default/cap. It stops short of describing result ordering or error behavior, so not a 5.

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?

Four compact sentences, all front-loaded with the primary action first, then filter sourcing, then pagination mechanics, then the sibling alternative. No filler or redundancy.

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-value documentation is unnecessary. The description covers scope, sibling routing, filter sourcing, and pagination well enough for an agent to call the tool correctly, leaving no significant gap for a 9-parameter browse tool.

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 the baseline is 3. The description notes multi-value filters accept comma-separated values and restates the limit default (10) and cap (30), but the comma-separated syntax is already documented per-parameter in the schema, so the added meaning is marginal.

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 ('Browse Rotten Tomatoes TV series results') and explicitly names the sibling tools it is not: rottentomatoes_browse_movies for movies and browse_filters for filter values. An agent can distinguish it from its siblings without opening a 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?

Gives explicit when-to-use routing: consult rottentomatoes_browse_filters with list=tv_series_browse for current filter values, and use rottentomatoes_browse_movies for movies. The condition that selects each alternative is spelled out, not left to inference.

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