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 useful context beyond them: paginated title cards, that results contain Metascore and user score, and notably that access is credential-free public data. Rate limits and pagination behavior are the only notable omissions.

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?

Front-loads purpose, then return shape, then access note, then the detail alternative. Efficient and readable, though the trailing parameter restatements duplicate the schema and cost some space.

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 not required; the description still notes the card contents. Purpose, filtering/sorting, pagination, access model, and a routing hint to a sibling are all present for a read-only 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 coverage is 100%, so all five parameters are already documented. The description largely restates the schema (page default 1, per_page default 24 clamped to 100) and adds no semantics beyond it, so the 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 and resource ('Browse Metacritic titles by content type') plus the optional dimensions (genre, sort). It names the sibling metacritic_game as the detail alternative, so it is differentiable, but it does not distinguish itself from the parallel metacritic_movie/metacritic_tv detail siblings, leaving some ambiguity about the browse-vs-detail split for non-game types.

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?

Provides one explicit alternative ('Use metacritic_game to get a Metacritic game'), which rescues it above pure implication, but gives no guidance for movies or TV (metacritic_movie, metacritic_tv exist) and no when-not-to-use or prerequisite context.

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