seerr_get_movie_ratingscombined

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

With annotations declaring readOnlyHint=true, the description adds the useful context that the tool returns combined RT and IMDB ratings. It does not contradict the annotations. However, it doesn't detail what 'combined' means (e.g., separate fields vs. a single score) or any other behavioral traits like availability or data freshness, but the output schema reduces the need for such details.

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?

The description is a single, succinct sentence that immediately communicates what the tool does. It is front-loaded and contains no irrelevant information, earning a perfect score for conciseness.

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?

The tool is simple with one parameter and has an output schema. The description adequately covers the main purpose. It could be more explicit about what 'combined' means, but given the output schema and the readOnlyHint annotation, the description provides sufficient context for an agent to select and invoke the tool correctly.

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?

The schema only provides movie_id as an integer without a description. The description mentions 'movie' ratings, clarifying that the ID refers to a movie. However, it does not explain the ID type (e.g., TMDB ID) or where to obtain it, leaving the parameter semantics only partially clarified.

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 verb (Get), the resource (movie ratings), and the specific combination (RT and IMDB). It effectively distinguishes this tool from siblings like seerr_get_movie_ratings by specifying the combined nature of the ratings.

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: use this tool when you need both RT and IMDB ratings for a movie. However, it provides no explicit guidance on when to choose this over seerr_get_movie_ratings or other rating tools, and it doesn't mention any exclusions or alternatives.

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