NBA Player Game Log

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint as true/false. However, the description does not add any behavioral context beyond the basic function, such as whether results are paginated (despite a limit parameter) or the range of seasons available.

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?

The description is a single sentence with no wasted words, but it is overly concise and omits essential information about parameters and output. It is front-loaded with the core purpose but lacks structure to support parameter usage.

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?

Given 7 parameters, no output schema, and sibling tools like nba_team_game_log, the description is severely incomplete. It does not explain what data is returned, how to filter by date or season type, or how it differs from nba_team_game_log. Minimum viable completeness would require parameter descriptions and usage context.

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?

With 0% schema description coverage, the description must compensate but fails to explain any parameters beyond the implied 'player' and 'season'. Parameters like limit, dateFrom, dateTo, leagueId, and seasonType are not described, leaving the agent without guidance on valid formats or defaults.

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?

The description clearly states the verb 'Get' and the resource 'game-by-game statistics for an NBA player in a season.' It distinguishes itself from sibling tools like nba_team_game_log (team-based) and nba_player_career_stats (career summary) by specifying per-game granularity.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or limitations. For example, it lacks context like 'Use this for detailed per-game stats; for season averages, use nba_player_career_stats.'

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