Icu Get Seasons

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

While annotations cover safety, the description adds critical operational behavioral traits, specifically that 'A season runs until the day before the next one starts' and that 'the newest season is open-ended.' This is crucial business logic not 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 description is highly efficient, front-loading the core purpose first, followed by usage context, and finally, specific technical constraints. Every sentence adds significant value.

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?

The combination of functional explanation, workflow integration with dependent tools, and defining season boundaries makes this definition exceptionally complete for an agent.

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?

With 100% schema coverage, the description does not need to elaborate on the nature of the parameters. It provides context (for coaches managing multiple athletes) but does not add semantic meaning beyond the schema's definition. Baseline score 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 immediately and clearly states the function ('List the athlete's training SEASONS') and identifies the data returned (name, start, end, curve ID). It is highly distinct from sibling tools.

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?

It provides clear usage scenarios ('which seasons do I have?') and explicitly defines the sequence of use, directing the agent to call `icu_get_power_curves` after retrieving the season's `curve_id`.

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