metacritic_movie_critic_reviews

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

With no annotations, the description carries the behavioral burden. It discloses pagination, return fields, and that data is public. However, it does not mention sorting behavior, rate limits, or error conditions (e.g., invalid slug), leaving some gaps.

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?

Three concise sentences: action, return fields, and a note on accessibility. No wasted words. Front-loaded with the verb and resource.

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?

Given no output schema, the description partially covers return values but omits format details and sorting options. For a simple list tool, it is mostly adequate but missing some behavioral context like sort semantics.

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 description adds limited value beyond the schema. It mentions 'paginated' which contextually explains page/per_page, but sort order values are not explained. The return field list is helpful but does not directly clarify parameters.

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 clearly states the tool lists Metacritic movie critic reviews, specifying it returns professional/publication reviews. It distinguishes from sibling tools for other media types (game, TV) and user reviews by explicitly saying 'movie's critic reviews' and 'professional/publication reviews.'

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?

The description implies usage for retrieving professional reviews for a Metacritic movie. It notes pagination and credential-free access, setting clear expectations. While it doesn't explicitly exclude alternatives, the context of sibling tools (e.g., metacritic_game_critic_reviews) makes the domain clear.

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