Get TV show details

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

Annotations already indicate readonly and open world. The description adds that ratings come from OMDb (requiring OMDB_API_KEY) and defaults for region and language, providing useful behavioral context beyond annotations.

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?

Single, well-structured paragraph with main action upfront. Every sentence adds value without redundancy.

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?

Despite no output schema, the description thoroughly lists what is returned and explains the optional OMDb enrichment. It provides sufficient context for an agent to understand the tool's capabilities.

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 baseline is 3. The description adds that include_ratings defaults to true and that the id should come from search_tv, which adds meaning beyond the schema.

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 specifies 'Get full details for one TV show by TMDB id' and lists returned fields (overview, genres, seasons/episodes counts, networks, status, certification, links, ratings). This clearly distinguishes it from siblings like get_movie or get_tv_season.

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?

It directs users to obtain the id from search_tv and explains when to set include_ratings=false. While it doesn't explicitly exclude alternatives, the context is clear enough for an agent.

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