nba_teams

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

No annotations are provided, so the description carries full burden. It transparently states it returns ALL teams (no filtering), which is meaningful behavioral context for a zero-parameter tool. However, it says nothing about output shape, ordering, or whether results are cached/live. For a trivial read-only list tool this is acceptable but not rich.

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?

A single, front-loaded sentence with zero waste. Ideal size for a parameterless list operation.

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?

For a zero-parameter, read-only enumeration with no output schema and no annotations, the description conveys everything needed to invoke it correctly. Minor incompleteness (no mention of return format) is acceptable given the simplicity, but not fully exhaustive.

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 tool has zero parameters, which per the rubric establishes a baseline of 4. The description accurately reflects that no input is needed, and there is no parameter information to omit.

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 a specific verb and resource ('List all NBA teams'), which is clear and unambiguous. It distinguishes itself from siblings like nba_players and nba_games by naming the 'teams' resource explicitly. The only gap is that it doesn't differentiate itself from other sports team listings (e.g., espn_team_info), but within the NBA namespace the distinction is 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?

There is no explicit guidance on when to use this tool versus alternatives. The 'List all' phrasing implies it returns the full set with no filtering, which is a usable signal, but the description does not name a sibling or state when a filtered/parameterized alternative should be preferred. Baseline 3 for implied usage.

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