tmdb_tv_reviews

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

With no annotations, the description carries the full burden. It does mention the return format ('Formatted string') and parameter defaults, providing some behavioral insight. However, it does not disclose read-only status, rate limits, error handling, or other edge cases, which limits transparency.

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 concise and well-structured: a single-purpose sentence followed by Args and Returns sections. Every element earns its place, and the purpose is front-loaded.

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, and the description covers purpose, parameters, and return type. However, it lacks usage context (when to prefer over similar tools) and behavioral caveats (safety, errors). Given the absence of annotations, additional context would make it more complete.

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 0%, so the description's parameter details are vital. It explains series_id is required, language defaults to en-US, and page defaults to 1, adding meaning beyond the raw schema types and defaults. It could be even more explicit about language code format, but it is adequate.

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 action ('Get the reviews'), the target resource ('a TV show'), and the source ('TMDB'). It also inherently distinguishes itself from the sibling tmdb_movie_reviews by explicitly targeting TV shows, not movies.

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 alternatives like tmdb_movie_reviews or tmdb_search_movies. The description simply defines what the tool does without any exclusions, prerequisites, or recommendations.

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