balldontlie_nba_standings

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds the requirement of a BALLDONTLIE_API_KEY and warns that the return shape is unverified from vendor docs, providing useful operational context beyond what annotations supply.

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 structured with sections (Returns, Note, Example, Auth) and contains only relevant details. It is slightly verbose due to the return shape block, but each part adds value.

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 single-parameter read-only tool with good annotations, the description covers the return shape (though unverified), an example, and auth. It lacks detail on supported seasons and exact field semantics, but is reasonably 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 schema already describes season as 'Season start year' (100% coverage). The description adds an example with season=2023 but no additional semantic detail such as supported year ranges or format.

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 'NBA standings for a season,' clearly identifying the resource (NBA standings) and the scope (season-based). It does not use an explicit verb like 'get' or 'retrieve,' and it does not differentiate from other standings tools among siblings, so it's clear but not fully distinguishing.

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 when standings for an NBA season are needed, with an example showing season=2023. However, it provides no guidance on when to choose this balldontlie tool over other standings tools like apisports_basketball_standings or nba_standings, and no exclusions.

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