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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral context by warning that a league without a current matchday may return not found, which is useful for error handling, though it says nothing about result volume or pagination.

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; the primary capability is front-loaded and the alternative-tool routing follows immediately. Every clause 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?

A single required parameter with full schema documentation, an output schema to cover return values, annotations carrying the safety profile, and an explicit not-found caveat. Nothing an agent needs to invoke it correctly is missing.

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 description coverage, the schema already explains that league_shortcut must be the exact shortcut from openligadb_leagues including original case. The description only restates 'one league shortcut' and adds no format or lookup detail beyond the structured field, so the baseline 3 is 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?

States a specific verb and resource ('Get fixtures and results in OpenLigaDB's current matchday for one league shortcut') and distinguishes itself from siblings by naming openligadb_current_group and openligadb_matches. An agent can tell what it returns and how it differs from nearby tools without opening a schema.

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 routes the agent to openligadb_current_group for a group id and openligadb_matches for a whole season, plus warns that a league without a current matchday may return not found. It doesn't address openligadb_matchday_matches (a specific matchday by number), which is the closest alternative, so it falls short of full 5 coverage.

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