nba_schedule

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

Beyond the annotations (readOnly, openWorld, idempotent), the description reveals the payload size (~8 MB), the exact return structure with leagueSchedule/seasonYear/gameDates, and that no authentication is needed. These are concrete behavioral facts that help an agent anticipate cost and parse output.

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 four sentences, each with a distinct purpose: scope, performance warning, return format, and auth. It is front-loaded with the core purpose and contains no redundant phrasing.

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 a simple no-input data retrieval, and the description covers all essential aspects: what data is returned, how large the response is, when to use an alternative, and the response shape. This is complete for an agent to invoke correctly.

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?

With zero parameters, the input schema is already complete. The description adds no parameter-specific detail, which is appropriate given the tool takes no arguments. Per the rubric, a baseline of 4 is appropriate.

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 states 'Full league schedule for the current season (every game, date, broadcasters, arena)' which is a specific verb-resource combination. It also differentiates from nba_scoreboard_today by recommendation, making the tool's niche clear.

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 explicitly says 'Large payload (~8 MB) — prefer nba_scoreboard_today for just today,' naming an alternative and giving a clear condition for not using this tool. This provides explicit when-not/alternative guidance.

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