mlb_schedule_postseason_tunein

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

Annotations already declare read-only, open-world, and idempotent behavior, and the description does not contradict these. It adds valuable context by stating 'Auth: none needed' and describing the return structure, but it does not disclose behavior when the optional 'season' parameter is null (e.g., defaults to current season).

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 compact and front-loaded with the core purpose, followed by the return format and auth requirement. Every sentence serves a purpose with no redundancy or promotional content.

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 read-only tool with no output schema, the description covers the purpose, auth, and return structure. However, it does not explain the default behavior of the optional parameters, leaving a minor gap in how to invoke the tool without specifying a season.

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%, with both parameters already documented ('Season year.' and 'Sport id (1 = MLB).'), so the baseline is 3. The description adds no additional information about parameter meanings, defaults, or how they affect the response.

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 identifies the tool as providing postseason broadcast 'tune-in' info (where/when to watch playoff games), which distinguishes it from sibling schedule tools like mlb_schedule_postseason and mlb_schedule_postseason_series. It lacks an explicit verb such as 'Get' or 'List,' but the resource and scope are 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?

Usage context is implied by the 'tune-in' framing and the return type, but there is no explicit statement of when to use this tool versus alternatives. No prerequisites, exclusions, or alternative tool names are mentioned in the description.

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