Get Schedule

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

The description adds behavioral context beyond the readOnlyHint annotation by explaining that the tool returns matches organized by date, includes team names, venues, kick-off times in UTC and local venue time, and supports timezone conversion. No contradictions with annotations.

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 two sentences, front-loading the core purpose in the first sentence. Every sentence provides essential information without 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?

The description explains the output structure (daily matches with team names, venues, times in UTC and local) without needing an output schema. It covers optional parameters and default behavior. Minor missing details like empty responses for no matches are not critical for a schedule 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 coverage is 100%, so parameters are documented. The description adds value by explaining that filtering by date range selects a subset of the full schedule and that the timezone parameter converts match times. This clarifies the effect of parameters beyond their schema definitions.

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 retrieves the full FIFA World Cup 2026 schedule organized by date. It specifies that each day includes all matches with details, distinguishing it from sibling tools like get_matches (individual match details) or get_bracket (tournament bracket).

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 mentions optional date range filtering and timezone conversion, implying when to use these features. However, it does not explicitly state when not to use this tool or suggest alternatives, such as using get_matches for specific match details.

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