seerr_get_tv_ratings

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

The annotation readOnlyHint=true already indicates a safe read operation. The description adds no additional behavioral context, such as rating sources, aggregation, or response format. It does not contradict the annotation, but it also provides little beyond the annotation.

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 extremely brief with no filler or repetition, but it is under-specified. It is concise in word count but lacks substance, so it earns a middle score rather than a higher one.

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?

Although the tool is simple (one integer parameter) and an output schema exists, the description provides no context about what 'ratings' includes, how to interpret the output, or any domain-specific details. It is barely more informative than a tautology.

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 input schema has one required parameter 'tv_id' with no description, and the tool description does not explain its meaning or expected format. The parameter name is somewhat self-explanatory (TV identifier), but since schema coverage is 0%, the description should have compensated by clarifying the parameter, which it does not.

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 'Get TV ratings' clearly states a specific action (get) and resource (TV ratings), and the tool name distinguishes it from sibling 'seerr_get_movie_ratings'. However, it lacks any detail about what ratings are included or how they are presented.

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 provides no guidance on when to use this tool versus alternatives. There are no context signals about use cases, prerequisites, or exclusions, leaving the agent to infer solely from the name.

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