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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful scope by saying the data covers the most recent games in the feed and includes the last game date, but it does not clarify pagination, limit interaction, or data completeness. This is moderate added value, not rich behavioral detail.

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 a single efficient sentence that front-loads the returned metrics. It contains no filler, though it could be slightly more explicit about scope and default behavior.

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 read-only retrieval tool with no output schema and full schema descriptions, the description adequately conveys the returned content. However, it omits default limit behavior and sibling routing, leaving it only minimally complete for an agent choosing among many NBA tools.

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 100%, so the team, limit, and player parameters are fully documented in the input schema. The description does not add syntax, default, or filtering semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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 the resource and returned metrics: average minutes and plus-minus per player across recent NBA games, with last game date. It is clear what the tool provides, but it does not distinguish itself from nearby siblings like invoke_nba_projections or invoke_nba_player_pool.

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. It does not mention invoke_wnba_rotations, invoke_nba_projections, invoke_nba_player_pool, or any condition for choosing rotation averages over other NBA data tools.

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