get_season

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

No annotations are provided, so the description bears full responsibility for behavioral cues. It discloses the primary action (listing episodes) and preference for 'imdb_id', but fails to specify behavior when neither 'imdb_id' nor 'title' is provided (both are optional in schema), or potential side effects like rate limiting or authentication requirements.

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 extremely concise at two sentences, front-loading the core purpose. Every word is purposeful with no fluff.

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 output schema exists (confirmed by context signals), so return details are covered. The description specifies the input requirements and preference. It doesn't mention pagination or error handling, but for a basic listing tool, this seems 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?

Input schema coverage is 100%, with clear descriptions for each parameter. The description adds that 'imdb_id' is preferred and season is 1-indexed, but these are already in the schema. No additional semantic value beyond what the schema provides.

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 lists all episodes in a given season of a series, with a specific verb ('list') and resource ('episodes in a given season'). It also mentions using either 'imdb_id' or 'title', distinguishing it from sibling tools like 'get_by_imdb_id' and 'get_by_title', which search for series metadata.

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?

The description provides usage guidance by stating 'Provide either `imdb_id` (preferred) or `title`', indicating when to use each parameter. However, it does not explicitly exclude this tool over alternatives like 'get_episode' for individual episodes, or mention prerequisites, but the context is clear enough.

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