NBA League Player Stats

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds valuable behavioral context by noting 'Results are limited by default,' which informs the agent about default pagination (limit=25). This goes beyond what annotations provide.

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 extremely concise: two short sentences that directly state the tool's purpose and a key default behavior. Every sentence adds value without redundancy.

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 8 parameters (1 required) and no output schema, the description fails to provide essential context. It does not describe the structure of returned statistics, pagination behavior beyond 'limited', or how parameters like teamId or measureType affect results. This leaves the agent underinformed for a tool with moderate complexity.

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 0%, so the description must compensate for parameter understanding. However, the description does not explain any of the 8 parameters (e.g., season format, perMode options, leagueId meanings). The agent is left to infer from schema defaults and enums, which is insufficient for correct invocation.

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 uses a specific verb ('Get') and resource ('league-wide player statistics') clearly indicating the tool's function. It distinguishes itself from sibling tools like nba_league_team_stats (team stats) and nba_player_career_stats (career stats) by focusing on league-wide player stats for a season.

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 implies the context for use (league-wide player stats per season) but provides no explicit guidance on when to use this tool versus alternatives like nba_player_career_stats or nba_team_game_log. It lacks clear 'when to use' and 'when not to use' instructions.

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