get_shows_by_id_seasons_by_season_translations

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds only the basic retrieval/filtering behavior (returns season translations, optional language filter), which is consistent with the annotations but does not disclose substantial additional behavioral context such as pagination or ordering.

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 short, front-loaded with a clear summary, and follows with an endpoint and a compact Args block. Every line earns its place and the structure is easy to scan.

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?

Given the output schema, strong annotations, only three flat parameters, and a self-explanatory endpoint path, the description is complete enough for an agent to invoke the tool correctly. Return values are covered by the output schema, so the description does not need to explain them.

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 0%, so the description must compensate, and it does document all three parameters. It explains id as an id/slug, season as a season number, and language as a 2-character language filter, adding meaning beyond the bare schema types and titles. It could be slightly more explicit that language is optional, but the schema already provides that default.

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 opens with a specific verb and object, 'Get all season translations,' and the endpoint path clarifies that the resource is a show's season translations. It is clear, though it does not explicitly differentiate itself from sibling translation tools such as show-level or episode-level translations; that distinction must be inferred from the path.

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 guidance is given about when to use this tool versus sibling tools like get_shows_by_id_translations or get_shows_by_id_seasons_by_season_episodes_by_episode_translations. The endpoint implies the scope, but there are no explicit alternative conditions or exclusions.

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