espn: Get scoreboard

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. Description adds useful context that it returns 'current scoreboard with game status, scores, and basic game info' and supports date-specific queries, which supplements the annotations.

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?

Single concise sentence front-loading the key purpose and return contents, with no extraneous information.

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?

Describes return fields adequately for a list tool, but lacks details on pagination or behavior when limit is not specified. With 4 parameters and no output schema, the description provides reasonable completeness for a straightforward scoreboard tool.

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% with clear parameter descriptions (e.g., YYYYMMDD format for dates, sport/league code examples). Description adds no additional parameter semantics beyond the schema.

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 the verb 'get' and resource 'scores' (scoreboard). Specifies 'live or date-specific' and lists return fields (game status, scores, basic game info). Distinguishes from siblings like espn_get_event_summary and espn_get_team_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?

Implies use for scoreboard queries via 'live or date-specific scores' but provides no explicit guidance on when to use this tool vs alternatives (e.g., ncaa_get_scoreboard, nhl_get_scores) or when not to use it.

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