nba_schedule

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

Discloses large payload (~8 MB) and provides a partial return structure. No annotations exist, so the description covers size and structure but lacks details on read-only nature or authorization. Still helpful for an agent.

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?

Two concise sentences with front-loaded purpose, size warning, alternative tool mention, and return structure example. Every sentence adds value with no redundancy.

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, no output schema, and a straightforward purpose (return schedule), the description covers all needed context: what it does, payload size, alternative tool, and return format. Fully 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, and schema description coverage is 100%. Baseline score of 4 applies since description adds no parameter info (none needed).

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?

Description clearly states it returns the full league schedule for the current season with specific details like games, dates, broadcasters, arena. It distinguishes from sibling nba_scoreboard_today by noting that tool is for today only.

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?

Explicitly advises to prefer nba_scoreboard_today for just today, providing clear guidance on when to use this vs. an alternative. No other usage notes needed for a 0-parameter tool.

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