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

With no annotations, the description carries the burden and does disclose meaningful behavior: results are limited to competitions with upcoming games carrying odds, and each row includes a game count. It does not state read-only nature, ordering, or whether competitions without odds are excluded entirely, leaving gaps.

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 short sentences with zero waste, front-loading the returned resource and following with the routing purpose. Nothing redundant or padding.

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 no-parameter, annotation-free lookup tool with no output schema, the description conveys enough: what entities are returned, the odds/upcoming-game filter, and the presence of game counts. A brief note on result ordering or whether names are unique would have made it complete.

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 takes zero parameters, so there is nothing for the description to disambiguate at the argument level. Baseline 4 applies; the description adds value only by clarifying the implicit server-side filtering.

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 (list) and resource (basketball competitions), and adds scope qualifiers: only competitions with upcoming games that have odds, plus a per-competition game count. This clearly separates it from siblings like list_games and get_game, which operate at the game level.

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?

It explicitly gives the calling context: 'Use it to find the exact competition name for the other tools,' which tells the agent this is a discovery/lookup step before invoking other tools. It does not name an alternative or state when not to use it, so a 5 is not warranted.

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