nba_boxscore

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

With no annotations, the description carries the full burden. It discloses that the tool works for live and final games, includes per-period breakdown, and provides a sample return structure. It does not disclose potential error handling, data freshness, or authentication requirements, which are reasonable gaps given the tool's simplicity.

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 three sentences, front-loading the core purpose and then providing parameter source and return structure. Every sentence adds value, and there is 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?

For a single-parameter tool with no output schema or annotations, the description covers the key aspects: what it does, how to get the parameter, and what is returned. Minor omissions like error scenarios are acceptable given the tool's simplicity.

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 input schema is minimal (type string only) with 0% coverage. The description adds meaning by stating that gameId 'comes from nba_scoreboard_today or nba_schedule', guiding the agent on value provenance. This compensates for the schema's lack of description.

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 explicitly states the tool returns 'Live/final box score for one game' with per-player and per-team stat lines by period. It identifies the source of gameId (nba_scoreboard_today or nba_schedule), distinguishing it from sibling tools like nba_scoreboard_today which lists games.

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 clearly indicates where to obtain the gameId parameter, providing context for use. However, it does not explicitly state when not to use this tool or list alternatives beyond the gameId source. The guidance is helpful but not exhaustive.

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