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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds behavioral context about rejecting movies and the constraint to provide only one identifier. It does not describe the response format or what happens if no identifier is provided, but given the annotations, the added value is moderate. No contradiction with annotations.

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 with no fluff. It front-loads the primary output (one season in full) and lists the content fields, then immediately covers identifier selection and series-only constraint. Every sentence carries essential information, and the structure is logical and scannable.

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 is fairly complete for a read-only tool: it lists the content returned, explains the identifier options, and notes the series-only restriction. However, it does not explicitly state that at least one of id/query/imdb_id is required (it says 'provide only one' but not that one must be provided), and there is no output schema to clarify return structure. Given the absence of an output schema, the description could benefit from mentioning the response format or a note about required identifier, making it slightly incomplete.

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 description coverage is 100%, so all five parameters are documented. The description adds meaningful semantic constraints beyond the schema: it clarifies that id, query, and imdb_id are mutually exclusive (provide only one) and that season is optional and defaults to the latest. This helps an agent understand the relationships and usage of parameters, which the schema alone does not convey explicitly.

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 that the tool returns one season of a TV series in full, listing specific content (episode titles, airdates, runtimes, ratings, summaries, stills). It distinguishes from movies by noting series-only, but does not explicitly differentiate from the sibling tools tv_episode and tv_episodes, though the focus on a season vs. individual episodes is implicit. The verb 'accepts' and resource 'TV series season' are specific, making the purpose clear.

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 context: it accepts three identifier types (show title, TMDB id, IMDb id) and instructs to provide only one, and to omit season for the latest season. It also states 'Series only - movies are rejected with guidance,' which is an exclusion. However, it does not mention when to use this tool instead of the sibling tv_episode or tv_episodes tools, nor any explicit when-not-to-use conditions beyond movies. The guidance is partial but not misleading.

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