balldontlie_nba_players

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

The description discloses that the response shape is from vendor docs and unverified, advises inspecting the actual payload, and notes that a personal API key (BALLDONTLIE_API_KEY) is required. These details go beyond the readOnly/openWorld/idempotent annotations, providing important reliability and authentication context.

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 concise and well-structured: purpose, return shape, caveat, example, auth. Each section earns its place with no filler. The only minor issue is the inclusion of a detailed return shape, which is useful but somewhat lengthy.

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 simple search/resource tool with no output schema, the description provides the approximate return shape, pagination fields, an example, auth requirements, and a verification caveat. While it could mention error handling or rate limits, the provided details are sufficient for the tool's apparent complexity.

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?

Schema coverage is 100%, so the schema already documents all parameters (cursor, search, per_page, team_ids). The description adds a concrete usage example ({"search": "curry"}) but doesn't explain parameter semantics beyond the schema, so the baseline of 3 applies.

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 'NBA players, searchable by name' clearly identifies the tool as providing NBA player data, distinguishing it from sibling balldontlie tools for teams, games, stats, etc. The example 'Search a player' implies an action, even though there's no explicit verb like 'list' or 'get'.

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 for retrieving NBA player data by name, but does not explicitly contrast with alternatives like balldontlie_nba_teams or other siblings. There's no 'use this when' or 'instead of' guidance, leaving the agent to infer from context.

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