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 only 'paginated', which is already implied by the page/per_page schema parameters, so it contributes little behavioral context beyond the structured fields.

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 tight phrase with the resource front-loaded and zero filler. Nothing to trim; though also nothing extra.

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 explained, and annotations cover safety. However, for a tool with four parameters and close siblings, the description is bare-bones — no pagination ceiling, no slug sourcing, no sibling routing — leaving it only minimally complete.

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 slug format, sort values, and per_page clamping are all documented in the schema. The description adds no parameter meaning of its own; baseline 3 applies when the schema carries the burden.

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 names the exact resource — Metacritic movie *user* reviews — which implicitly distinguishes it from the sibling metacritic_movie_critic_reviews and metacritic_tv_user_reviews. The verb is only implied ('reviews' as a fetch), but an agent can identify the target 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?

There is no guidance on when to use this vs metacritic_movie_critic_reviews, metacritic_movie, or metacritic_game_user_reviews, and no mention of prerequisites such as needing a valid slug first. It states what it returns but never when it is the right choice.

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