Get TV season

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

Annotations declare readOnlyHint=true, confirming no destructive actions. The description goes beyond annotations by detailing the response content (overview, episode list, air dates, runtimes, ratings) and the special behavior of season 0. No contradictions.

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 efficiently convey purpose, content, and a key usage hint. No redundant words, and critical information is 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?

The description covers purpose, prerequisite, and response content sufficiently for a simple read-only tool with two parameters. It doesn't mention error conditions or rate limits, but the annotations and schema cover the core aspects. Reasonably complete.

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% with both parameters described (TMDB id and season number with minimum). The description reiterates the schema's info about season 0 being specials but does not add significant new meaning beyond the schema. Baseline 3 is appropriate.

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's function: retrieving a specific TV season's overview and episode list with details like air dates, runtimes, and ratings. It distinguishes from sibling tools like get_tv and get_tv_episode by focusing on a single season. The mention of season 0 as specials adds specificity.

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 a clear prerequisite ('Get the show id from search_tv') and implies the tool is for retrieving a season's details. It does not explicitly state when to avoid this tool or compare to alternatives, but the context of sibling tools makes the usage clear enough.

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