openligadb_season_matches

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

Adds a size warning (~550 KB) and explicit response schema, auth requirement, and example, going beyond the readOnly/idempotent/openWorld annotations. No contradictory behavioral claims.

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?

Front-loaded with purpose and size warning; the Returns block is efficiently structured and the example is compact. Every sentence contributes 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?

Covers purpose, size, alternative, auth, example, and full return structure. Without an output schema, the description takes on that responsibility and fulfills it completely.

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%, providing baseline 3. The description's concrete example (league:'bl1', season:'2024') adds a real-world mapping that the schema's terse descriptions don't fully convey, earning an extra point.

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 it returns every match in a league season with results. It distinguishes itself from the sibling matchday tool by warning about large size and recommending the matchday tool for smaller scope. The Returns: block specifies exact content.

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 says 'prefer the matchday tool' for the large payload, indicating when not to use this tool. The example shows how to request a whole Bundesliga season, and 'Auth: none needed' covers prerequisites. This provides clear when-to-use context.

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