openligadb_leagues

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

Annotations already cover read-only/idempotent/open-world behavior, and the description adds meaningful context: the exact return shape, estimated size (~819 entries, ~120 KB), an example, and that no auth is needed. This goes beyond the annotations' basic safety hints.

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 compact and front-loaded: it states the purpose in the first line, then provides a concise return example, size estimate, and auth note. No fluff or redundancy.

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 zero-parameter read-only tool, the description is thorough: it covers what is returned, gives an example, notes size, and states auth requirements. Without an output schema, it provides enough detail for an agent to understand and consume the result.

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?

The input schema has zero parameters, so the baseline is 4. The description adds semantic clarity by showing the output fields like leagueShortcut and leagueSeason, which is useful for downstream tool usage, even though no parameter-specific details are needed.

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 returns 'every competition + season OpenLigaDB carries' and explicitly frames its purpose: to 'find the league shortcut and season year the other tools need.' This is a specific verb+resource (list leagues/seasons) and directly distinguishes it from sibling tools that consume these identifiers.

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 says to call this when you need the league shortcut and season year for other tools, providing clear usage context. It does not explicitly list when not to use it or name alternative sources, but the intended sequencing is evident from the dependency it highlights.

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