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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that odds are only 'when available' and that rows carry schedule status, which is useful, but it says nothing about pagination, date defaults, or volume of returned rows.

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 filler: the capability and its payload come first, then the alternative-tool routing. Front-loaded and appropriately sized.

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?

An output schema exists, so return values need not be explained, and the description plus rich schema cover what an agent needs to call it. Minor gaps remain around date defaults and result volume, but nothing blocking.

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 the five parameters are fully documented in the schema, and the description adds only the sport+league scoping already implied there. No extra syntax, formats, or interactions (week vs dates vs seasontype) are explained, so the 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?

Starts with a specific verb (Fetch) and names the exact resource and payload contents: ESPN game rows with scores, schedule status, and odds, scoped to a sport and league. It also distinguishes itself from named siblings, so an agent can identify it without opening a schema.

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?

It explicitly routes the agent to alternatives with conditions: espn_game_summary for a single game's recap, espn_standings for tables, espn_rankings for rankings. It does not state exclusions for this tool itself (e.g., live-in-progress vs past dates), but the sibling routing is clear enough.

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