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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds one useful behavioral detail — that results come back as several result sets rather than a single table — but that detail is duplicated and nothing is said about pagination, rate limits, or what the result sets contain.

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 two identical copies of a single awkward sentence, with no front-loaded purpose statement and no structure. Half of the already-tiny text is pure redundancy.

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?

An output schema exists, so return-value explanation is not required, and the schema fully covers inputs. What is missing is sibling disambiguation among a crowded family of near-identically named player/team split tools — the one thing the description should supply — and it does not.

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%, with each of the six parameters documented (season format, per_mode, league_id, player_id source, season_type, measure_type). The description contributes nothing beyond that, which is the expected baseline when the schema does the work.

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 identifies a verb ('Get') and a resource ('one player's by clutch splits'), and 'one player' hints at the team-level sibling. But the phrasing 'by clutch splits' is garbled and the sentence is repeated verbatim, so the agent gets a rough idea of the resource without a clean statement of what distinguishes it from nba_player_clutch or nba_player_dash_by_game_splits.

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 when-to-use guidance, no mention of prerequisites (e.g., needing a player_id from nba-players), and no named alternative. An agent must infer from the name alone that this is the clutch-splits variant among several 'by_*' split endpoints.

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