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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds that a call returns exactly one page keyed to a single date/week/season selector, which is genuinely useful behavioral context, but says nothing about rate limits, failure modes for leagues lacking week tabs, or pagination.

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, zero waste, with the scope statement front-loaded and the prerequisite dependency second. Nothing is repeated from the title or schema.

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 an output schema present and annotations covering the read-only/open-world profile, the description only needed to convey scope and the catalog dependency, and it does both. Minor gap: it doesn't say what happens when a league page exposes no date/week tabs, leaving the agent to infer from the parameter docs.

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 each of the six parameters is already documented in the schema with sourcing and format notes. The description's "one date, week, or season page" hints that these selectors are alternative page modes, but adds no syntax or defaulting detail beyond what the schema states.

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?

"Fetch one date, week, or season page from Yahoo Sports' league schedule" names a specific verb and resource and bounds the scope to a single page rather than a whole season. It implicitly separates this tool from yahoo_sports_schedule_catalog by casting the catalog as the source of filter values, though it never states the sibling's role outright.

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?

"Use exact filter values from yahoo_sports_schedule_catalog" is an explicit prerequisite that routes the agent to the sibling tool before calling this one. It stops short of saying when not to use this tool (e.g. for team-scoped schedules, where yahoo_sports_team_schedule would apply).

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