get_episode

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

No annotations provided. Description implies a read operation but does not confirm safety, auth needs, or other behavioral traits. For a lookup tool, minimal disclosure, but full burden on description is partially met.

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, no waste. First sentence states purpose, second provides key usage guidance. Well 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?

With output schema present, return values need not be explained. However, description lacks guidance on the optional plot parameter and the case when both imdb_id and title are omitted (schema allows this, but description seemingly requires one). Adequate but with notable gaps.

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 covers 100% of parameters. Description adds value by grouping imdb_id and title as alternative identifiers with preference for imdb_id, and clarifies they are used together with season/episode. Slight conflict: schema marks imdb_id and title as optional (default null), but description implies one must be provided.

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 tool looks up a specific TV episode. It distinguishes from siblings like get_season (whole season) and search_movies (search) by specifying exact episode retrieval.

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 instructs to provide either imdb_id (preferred) or title plus season and episode, giving clear context. However, it does not explicitly exclude cases for siblings like get_by_imdb_id or get_by_title, though the episode focus differentiates.

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