get_season_episodes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it returns a list of episode info but does not mention that it is a read-only operation, potential error conditions, pagination, or that data comes from TMDB (though source is mentioned in Args). This is minimal coverage for a tool with no annotation fallback.

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 and well-structured, with a clear purpose line followed by Args and Returns sections. Every sentence serves a purpose with no wasted words, and the 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?

For a simple retrieval tool with only 3 parameters and no output schema, the description provides the essential purpose, args, and return type. However, it lacks contextual details such as expected output structure, edge cases, or confirmation that only TMDB is supported. It is adequate but not rich.

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?

The schema description coverage is 0%, so the description must compensate. It provides inline comments for all three parameters: source_id is 'media ID (tmdbid)', season_number is 'season number', and source is 'data source (tmdb)'. This adds meaning beyond the schema, though it does not detail formats or constraints beyond what the schema already indicates.

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 states '获取剧集的对应季的分集信息' (get episode info for the corresponding season of a series), which is a specific verb+resource. It distinguishes from siblings like get_media_details by focusing on season episodes. However, it does not explicitly differentiate from alternative tools that might provide similar data.

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?

No explicit guidance on when to use this tool vs alternatives. The purpose implies using it to fetch season episodes, but there is no mention of exclusions or comparison to sibling tools such as get_media_details or search_media_or_person. The agent must infer usage from the description alone.

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