get_shows_by_id_ratings

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds limited context by explaining that extended='all' includes external source ratings, but it does not otherwise disclose additional behavioral traits or response characteristics.

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 brief and includes the endpoint, arguments, and parameter explanations. There is no fluff, and the key parameter guidance is front-loaded, though the endpoint line is somewhat redundant with the tool name.

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 read-only tool with a simple two-parameter schema and an output schema already present, the description covers the essential semantics of a valid id and extended value. No auth details are needed given the annotations, and the description is sufficiently complete for an agent to 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?

Schema description coverage is 0%, so the description carries the burden for parameter meaning. It explains id as 'the id/slug of the resource' and extended as controlling inclusion of external ratings, which adds genuine meaning beyond the raw schema types.

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 states 'Get show ratings,' which names a specific verb and resource. However, it does not explicitly differentiate this from sibling tools such as get_movies_by_id_ratings or get_shows_by_id_seasons_by_season_ratings, though the resource is somewhat clarified by the endpoint.

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?

There is no guidance on when to use this tool versus the many rating-related siblings, and no exclusions or alternative tools are mentioned. The description gives only a minimal statement of what it does, leaving the agent to infer appropriate usage.

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