Teams Get Team Statistics

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the data categories returned (offensive/defensive/special teams, team and opponent), but says nothing about auth, rate limits, or whether the season is inferred.

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?

A single front-loaded sentence with zero filler — the resource and its scope are stated immediately and nothing is wasted.

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?

With no output schema, the description must carry more of the return-value burden; it names the statistical categories but not the response shape, granularity (per-game vs totals), or how the season is determined given no season parameter exists. Adequate but leaves real gaps for an agent to guess at.

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 67%; sport and league carry example values ('basketball', 'nba, eng.1') while team_id has no schema description. The description mentions 'team' but adds no format or value guidance for any parameter, so it does not compensate for the gap. Baseline 3 for moderate coverage.

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?

States a specific verb ('Fetch') and a well-scoped resource ('team and opponent season statistics across offensive, defensive, and special teams categories'). This is clearly distinguishable from siblings like teams_get_team (metadata), teams_get_team_roster, and teams_get_player_stats, though it does not name those siblings explicitly.

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 offers no when-to-use guidance, prerequisites, or alternatives. An agent gets no signal on how this differs in intent from teams_get_player_stats or teams_get_team — only the phrase 'team and opponent' implicitly narrows it.

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