mlb_schedule_postseason

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

Provides the return structure, which helps set expectations. However, no annotations exist, so the description should disclose more behavioral traits (e.g., data freshness, caching, rate limits). The output format is given but not deeply explained.

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?

Two sentences and an inline return structure make it concise. No filler, but could benefit from a bullet list for parameters.

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?

Covers basic purpose and output structure, but lacks parameter explanations and any mention of error conditions or limitations. For a tool with 4 optional params and no output schema, more detail is needed.

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?

With 0% schema description coverage, the description only vaguely mentions 'optionally a single season / series type'. It does not explain 'hydrate', 'sportId', or 'gameTypes' meaningfully. The mapping from 'series type' to parameters is unclear.

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?

Clearly states it returns postseason schedule for all playoff games, with optional filtering by season/series type. However, it does not explicitly differentiate from sibling tools like mlb_schedule_postseason_series or mlb_schedule.

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 other schedule tools. Mentions optional parameters but no context on best use cases or prerequisites.

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