get_scoreboard

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

With no annotations, the description carries the full burden. It states it returns current/upcoming games with scores and mentions NFL week support, but it does not disclose whether past games can be accessed, whether scores are live or final, or how the date parameter affects the 'current/upcoming' logic. This leaves significant ambiguity.

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, front-loaded with the core purpose, and contains no filler or redundant information. It is efficient and easy to scan.

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?

The tool is relatively simple, but without an output schema, the description should describe return structure or edge-case behavior. It does not mention response format, date handling for non-NFL leagues, or score status, leaving some gaps in contextual completeness.

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 provides 100% descriptive coverage for all parameters, so the baseline is 3. The description adds no new parameter semantics beyond repeating that week is NFL-only, which the schema already states.

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 a specific action ('Get current or upcoming games with scores') and resource, distinguishing it from siblings like get_schedule (schedule without scores) and get_game (individual game details). The NFL week note adds specificity without confusing the core purpose.

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 usage for scoreboard queries but does not explicitly contrast with alternatives such as get_schedule or get_game. The NFL week note is the only usage hint, providing no when-not-to-use guidance.

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