Get TV show details

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

Beyond annotations (readOnlyHint, openWorldHint), the description adds 'No sign-in required' and explicitly mentions the inclusion of the full episode list, providing nontrivial behavioral context. It doesn't cover return format or error cases, but the annotations already indicate a safe read operation.

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 two sentences, front-loaded with the primary purpose, and the second sentence adds a concise auth note. There are no redundant or unnecessary words.

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?

Given the tool's simplicity, good annotations, and complete parameter schema, the description adequately covers the primary purpose, auth, and episode list inclusion. Since there is no output schema, a bit more detail on return shape could help, but the current description is sufficient for a straightforward read-only fetch.

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?

All three parameters (imdbId, season, includeEpisodes) are fully described in the input schema, and the description adds no additional meaning or examples. Thus the baseline score of 3 applies.

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 uses the specific verb 'Fetches' with a clear resource: 'details for a single show by IMDb id'. It explicitly distinguishes this tool from siblings like shows_search and shows_popular by emphasizing the single-show lookup and the inclusion of the full episode list.

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?

Clear context is provided that this tool is for fetching details for a specific show when you have its IMDb id. While it doesn't explicitly name alternatives or exclusions, the 'by IMDb id' phrasing makes the intended use obvious.

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