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 the useful pagination framing and the shape of each review item, but does not mention rate limits, throttling, or auth needs.

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?

Two sentences with zero waste. The purpose and returned fields come first, and the alternative-tool routing is appended cleanly.

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?

For a paginated list tool with a full input schema, an output schema, and safety annotations, everything an agent needs to invoke it correctly is present: what it returns, how it paginates, and which sibling to prefer. Nothing material is missing.

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 page, slug, sort, and per_page are already documented in the schema. The description adds no kind of sort semantics, slug conventions, or pagination mechanics beyond the structured fields, 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?

Names a specific verb (Fetch) and resource (paginated professional-review items for a Metacritic TV show) and lists the fields returned (publication, score, quote, author, source URL). It explicitly distinguishes itself from metacritic_tv_user_reviews and metacritic_tv, so an agent can pick it 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?

States exactly when to use alternatives: metacritic_tv_user_reviews for user reviews and metacritic_tv for show details. The routing between sibling review/detail tools is fully resolved rather than left to inference.

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