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

Annotations only declare readOnly and openWorld; the description goes well beyond them by naming the upstream source (ESPN public site JSON), declaring UTC timezone semantics, stating the empty-result behavior, and disclosing the paid-call model including price, payment rails (x402 on Base/Solana/Arc) and that failed calls are not charged.

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?

Three front-loaded sentences: what it returns, then timezone/empty-result behavior, then cost. Every clause carries operational information an agent needs before calling, 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?

With an output schema covering return values and annotations covering safety, the remaining agent-critical unknowns are source, timezone, empty-day behavior and cost — all of which the description supplies. Nothing material is missing for a one-parameter read 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?

The schema already documents the single date parameter at 100% coverage, including the 'yesterday UTC' default. The description reinforces that dates are UTC-interpreted but adds no format or edge-case detail beyond what the schema states, 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?

States a specific verb and resource ('ESPN college football scoreboard for one date') and enumerates the payload fields returned (teams, score, status, stadium). The sport-specific naming cleanly separates it from dev_espn_nfl_scoreboard, dev_espn_nba_scoreboard and dev_espn_standings without needing to name them.

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?

Usage is implied by 'for one date' and the note that days with no games return an empty list, which tells the agent this is a date-scoped lookup rather than a search. However, there is no explicit routing guidance toward alternatives (e.g. standings, team stats, or other sports scoreboards) or any stated when-not condition.

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