ncaa_get_scoreboard

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

With no annotations, the description must disclose side effects, permissions, or data freshness. It states it returns scoreboard data but does not mention rate limits, authentication, or whether the data is real-time. The description is not contradictory but lacks depth.

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 two short sentences with no redundant information. It front-loads the purpose and succinctly covers the return type.

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?

No output schema is provided, and the description's 'basic info' is too vague. For a tool returning game scores and status, the description should detail the expected fields (e.g., team names, scores, period). This omission leaves ambiguity for the agent.

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 clear parameter descriptions for sport, division, and date. The tool description adds little beyond restating 'for a sport and division.' The baseline of 3 is appropriate as the schema already provides necessary context.

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 tool retrieves an NCAA scoreboard for a given sport and division, returning games with scores and status. This distinguishes it from siblings like ncaa_get_game (specific game details) and ncaa_get_schedule (upcoming 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 implies use for scoreboard data but offers no explicit guidance on when to use this tool versus alternatives like espn_get_scoreboard or nhl_get_scores. No when-not-to-use or prerequisite information is provided.

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