mlb_schedule

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds useful behavioral context by specifying the return shape and stating 'Auth: none needed', which goes beyond the annotations. No contradiction exists.

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. The first line states the core purpose, followed by a precise return-type block and the auth note. Every sentence serves a purpose with no filler.

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 no output schema, the description adequately documents the return structure. The parameter schema covers individual parameters, and the description adds the high-level usage (date vs. range, team filter). It is sufficiently complete for a read-only schedule tool, though it could mention the relationship between startDate and endDate more explicitly.

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 the baseline is 3. The description adds semantic value by tying date, startDate, and endDate together as range options and clarifying the optional team filter. This grouping helps an agent understand parameter combinations without reading each schema entry.

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 a game schedule, with options for a single date, a date range, and an optional team filter. It is a specific verb+resource ('Game schedule') but does not explicitly distinguish from sibling tools like mlb_schedule_postseason or mlb_schedule_tied.

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 clear context for when to use the tool: by single date or startDate/endDate range, optionally for one team. It does not give explicit exclusions or point to alternative tools for postseason schedules, but the usage context is clear enough for an agent to decide when to invoke it.

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