Get season and episodes

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that by listing the return payload (since no output schema exists) and flagging the specials case, though it says nothing about pagination or behavior on an invalid season number.

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?

Three tight sentences, front-loaded with the core purpose and return payload, then usage, then the specials caveat and the id dependency. Every sentence earns its place with no filler.

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?

For a read tool with no output schema, it compensates by listing the episode fields returned, and annotations cover safety. Missing only minor operational detail such as behavior for out-of-range seasons or how the language fallback interacts with episode overviews.

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% and each parameter is fully documented there. The description's 'Season number 0 holds the specials' merely restates the schema's own 'Use 0 for specials', and the language parameter is left entirely to the schema, so no new semantic value is added. Baseline 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?

States a specific verb+resource ('Get one season of a TV show with its full episode list') and enumerates the returned fields, which cleanly distinguishes it from get_tv_show (show-level) and the other siblings. An agent can tell exactly what this returns without opening the schema.

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?

Gives clear usage context ('Use it to answer questions about episodes, air dates or season length') and explicitly routes the agent to search_titles or get_tv_show for the required tv_id. It does not name a sibling to avoid or state exclusions, which keeps it short of a 5.

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