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

Annotations already declare the full safety/behavior profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds genuine context the annotations cannot: the upstream source (nflverse) and the coverage window (1999–current, 2024 season includes its Jan–Feb 2025 playoffs). It says nothing about return volume, pagination or result ordering, which is a modest gap for a full-season schedule pull.

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?

Front-loaded with the purpose and source, then the field inventory, then the filter options. Two sentences, no filler words. The field list is long but each item maps to real returned data, so it earns its space.

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?

There is no output schema, so the field enumeration in the description usefully stands in for a return-value spec, and the source plus 1999–current window is provided. Combined with 100%-covered parameters and complete read-only annotations, an agent has nearly everything needed; only pagination/volume expectations are unstated.

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%, with team abbreviations, week ranges (1–18 regular season plus playoffs) and the season coverage window all spelled out in the schema itself. The description's "filter by week and/or team" only restates the schema, adding no format or semantics beyond it. 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+resource (returns an NFL schedule and results for a season) and enumerates the returned fields — game ids, dates, kickoff, scores, spread/total, weather, QBs, coaches, referee — which implicitly separates it from siblings like nfl_play_by_play, nfl_injuries and nfl_team_game_log. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

"Filter by week and/or team" implies the intended query patterns, and the required season parameter implies a per-season scope. There is no explicit when-to-use guidance, no exclusions, and no pointer to nfl_team_game_log or nfl_play_by_play for adjacent needs, so an agent must infer routing.

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