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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The only behavioral detail added is 'as several result sets', which is marginally useful but repeated verbatim twice, and nothing is said about upstream latency, data completeness, or the per_mode/league_id constraints hinted at in the schema.

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 single sentence is duplicated word-for-word, wasting half the text, and the sentence itself is ungrammatical ('Get Returns ... splits splits'). Length is short but structure is broken rather than front-loaded.

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 six-parameter tool with an output schema and annotations, the description should explain what a 'game split' is and how the result sets are organized, but it says nothing. The agent is left to infer the semantics of the splits dimension entirely from the tool name.

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 every one of the six parameters is documented in the schema itself (season format, team_id provenance, defaults for per_mode/season_type/measure_type). The description adds no parameter meaning 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 text 'Returns one team's by game splits splits as several result sets' mostly restates the tool name in garbled form; the doubled word 'splits' and the empty verb phrase 'Get Returns' obscure rather than clarify. It conveys only that output arrives as multiple result sets, which is not a purpose statement an agent could use to distinguish this from nba_team_dash_by_clutch or nba_team_dash_by_last_n_games.

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 prerequisite, and no mention of any alternative tool. The many sibling dash tools (clutch, last-n-games, opponent, pt_*) are never referenced, so an agent gets no routing signal at all.

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