nba_scoreboard_today

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

No annotations provided, so the description carries full burden. It discloses the source (live CDN scoreboard) and the exact return structure. For a simple read-only tool, this is adequate transparency, though it could mention refresh rate or caching behavior.

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 concise and well-structured sentences. Front-loads key information: 'Today's games from the live CDN scoreboard'. No unnecessary words.

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 no parameters and no output schema, the description fully explains what the tool does and what it returns, including an example of the response structure. Complete and sufficient.

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?

No parameters exist, so there is no need for additional parameter info. The description adds value by explaining the return structure and purpose beyond what the empty schema provides, meriting a baseline 4.

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 it returns today's games from the live CDN scoreboard, including matchups, scores, game IDs. It explicitly distinguishes itself as the fastest way to get gameId values for nba_boxscore/nba_playbyplay, differentiating from these sibling tools.

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 directly tells when to use it: to get today's game IDs for other NBA tools. While it doesn't explicitly say when not to use it or list alternatives, the context is clear and implicit.

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