mlb_schedule_postseason

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

The description adds useful behavioral context beyond the annotations: it discloses the exact return shape (totalGames, dates with gamePk, seriesDescription, teams, status) and states 'Auth: none needed.' This complements the readOnlyHint and idempotentHint annotations rather than repeating them.

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 well-structured: two sentences for purpose, a three-line return format, and an auth note. Every sentence earns its place without redundancy or fluff.

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?

With no output schema, the description compensates by providing a return structure. It also covers auth and optional filtering. A minor gap is the lack of explicit default behavior when season is omitted, but the tool is otherwise adequately specified for its simplicity.

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%, so all four parameters are already described. The description's mention of 'optionally a single season / series type' maps to the season and gameTypes parameters but does not add significant meaning beyond what the schema provides. 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?

The description clearly states the tool returns the postseason schedule ('all playoff games') and supports optional filtering by season or series type. This distinguishes it from sibling tools like mlb_schedule (regular season) and mlb_schedule_postseason_series (series-specific detail), making the purpose unambiguous.

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 implies the primary use case: retrieve all postseason games, optionally filtered by season or series type. It does not explicitly exclude or reference alternatives, but the scope is clear enough that an agent would know when to select this tool.

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