list_seasons

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

No annotations provided, so description carries full burden. It discloses caching behavior via the refresh parameter ('bypass cache and re-fetch from Hudl'). No destructive actions implied, and the read-only nature is evident. Good for a list operation.

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?

Two sentences with no filler: first states purpose and ordering, second explains output and usage with sibling tools. Every sentence is informative and earns its place.

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?

No output schema exists, but description fully explains return fields with an example label. Also covers cache behavior via refresh parameter and integrates with sibling tools. Complete for the tool's simplicity.

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 100% with one boolean parameter 'refresh' described. Description adds value by explaining output fields (seasonId, label, seasonYear) and their usage, going beyond the schema which only documents the 'refresh' param.

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?

Description states clear verb 'List', resource 'seasons', context 'for the team', and sorting 'newest first'. It also specifies return fields (seasonId, label, seasonYear), distinguishing it from sibling tools that consume seasonId.

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?

Explicitly advises using the returned seasonId with get_team_stats, get_player_stats, or get_game_results, guiding the agent on when to use this tool to obtain season identifiers. Missing explicit when-not-to-use statements, but the context is clear.

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