NBA Stats Endpoint

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

Annotations already indicate readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, signaling safe, non-destructive, idempotent behavior. The description adds minimal behavioral context (only 'raw stats') beyond what annotations provide, so it does not significantly enhance transparency.

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, consisting of two sentences with no wasted words. However, it is too brief and lacks detail that would be valuable for effective tool usage.

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 the lack of output schema, low schema coverage, and vague description, the tool is incomplete. It does not explain return values, error handling, or how to correctly construct endpoint names and parameters. The description fails to provide enough context for reliable use.

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 description coverage is 0%, meaning no parameter descriptions exist in the schema. The description only mentions 'documented endpoint name and NBA parameter names' without explaining the parameters 'params', 'endpoint', or 'limitRows'. It adds some context but fails to compensate for the lack of schema descriptions.

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 it is an 'Advanced raw stats.nba.com endpoint caller' and mentions using a documented endpoint name. This distinguishes it from specific sibling tools like 'nba_league_player_stats' which target particular data types, but it lacks specificity about what the tool actually retrieves or does beyond calling an endpoint.

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 advises to 'Use a documented endpoint name and NBA parameter names' but does not provide guidance on when to use this generic caller versus the specific sibling tools. There are no explicit when-to-use or when-not-to-use conditions, nor any mention of alternatives.

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