openligadb_current_matchday

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds valuable behavioral details beyond that: the return shape ('a single object, not a list'), the exact fields returned, an example response, and an explicit 'Auth: none needed.' This contextualizes what to expect from the call.

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 well-structured: starts with purpose, then return type, then a concrete example, then auth note. Every line earns its place, with no redundant or vague language.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description is complete: it explains what the tool does, when to use it, the exact parameter format, the return structure, and auth requirements. No significant information is missing for an agent to invoke it correctly.

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 schema already provides 100% coverage with a description and default for the 'league' parameter. The description reinforces the semantics by showing a concrete usage example ('{"league": "bl1"}' for Bundesliga), which adds clarity beyond the schema alone.

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 purpose: 'Which matchday a league is currently on' and adds practical context ('resolve this week without guessing'). It distinguishes itself from siblings like openligadb_matchdays (list all matchdays) and openligadb_matchday_matches by focusing on the current matchday as a single object.

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 context for when to use the tool (need the current matchday, e.g., to resolve 'this week'), and includes a concrete example for Bundesliga. However, it does not explicitly name alternative tools or exclusion criteria, so it falls just short of full guidance.

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