euroleague_seasons

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

The description discloses the return shape ({total, data:[...]}), notes that no authentication is needed, and provides a concrete example — all beyond what the annotations (readOnlyHint, openWorldHint, idempotentHint) already convey. It doesn't discuss rate limits or pagination, but for a simple read-only season list, the added context is meaningful.

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 front-loaded with the core purpose, followed by a useful return-shape block, an example, and a brief auth note. Each section earns its place; the structure is cleanly organized, though slightly segmented.

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 simple tool with one optional parameter and strong annotations, the description covers the essentials: purpose, return shape (compensating for the absent output schema), an example, and auth requirements. No critical gaps stand out for this low-complexity tool.

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% (the enum parameter is fully described with 'E = EuroLeague, U = EuroCup'), so the baseline is 3. The description's example call ({'competition': 'E'}) reinforces usage but adds no new semantic meaning beyond the schema.

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 clearly states the tool's function with a specific verb and resource: 'call this to get valid season codes like E2024.' It distinguishes itself from sibling tools like euroleague_games or euroleague_rounds, which handle games and rounds rather than season metadata.

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 explicitly directs the agent to use this tool when it needs valid season codes, providing a concrete trigger ('call this to get valid season codes like E2024'). It doesn't name alternatives or exclusions, but the clear use-case phrasing gives sufficient contextual guidance for a simple lookup tool.

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