Get TV episode

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

Annotations already indicate readOnlyHint and openWorldHint. Description adds value by detailing return fields and workflow (prerequisite search), without contradicting annotations. Provides safe, non-destructive context.

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?

Two sentences, each purposeful: first defines action and output, second provides prerequisite. No unnecessary words, efficiently aids agent understanding.

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?

With no output schema, description lists return fields (overview, air date, runtime, rating, guest stars, director/writer). Covers key aspects for a simple read-only tool. Slightly lacks mention of possible zero results, but adequate.

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%, baseline 3. Description adds meaning by linking parameters to the retrieval logic ('by show id + season number + episode number') and clarifies 'id' as TMDB numeric id from search_tv.

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?

Description clearly states it retrieves a single TV episode by show id, season, and episode numbers, listing specific return fields (overview, air date, runtime, etc.). It distinguishes from siblings like get_tv_season (season-level) and get_tv (show-level).

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?

Explicitly states prerequisite: 'Get the show id from search_tv.' Implies use when you need episode-level details versus seasonal or show-level. No explicit exclusions but context sufficient.

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