Yılın resmî tatilleri

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds a valuable behavioral trait: religious holidays are embedded only for 2026 and 2027, and for other years it returns diniBayramlarDahil=false and omits them without guessing. This goes beyond annotations and clarifies an important edge case.

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 with the main purpose, followed by the year-specific limitation. Every sentence earns its place; no fluff. It strikes a good balance between brevity and necessary detail.

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?

With an output schema present (has output schema: true), the description does not need to explain return values. It covers the core behavior, the national/religious distinction, and the critical year limitation, which is sufficient for an agent to call it correctly. Nothing essential 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?

The schema fully describes the 'yil' parameter with min/max range and default (coverage 100%). The description does not add parameter-specific meaning; it focuses on tool behavior. The year limitation is more about behavior than parameter semantics, so it does not elevate the score beyond the schema-driven baseline of 3.

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 provides Turkey's public holidays for a given year, distinguishing between national (fixed) and religious (Diyanet calendar) holidays. It also highlights the year limitation, which implicitly differentiates it from a single-date holiday checker. The verb and resource are specific, making the purpose unambiguous.

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 gives clear context that this is for annual holiday lists, but it does not explicitly mention when to prefer this over the sibling 'tatil_mi' tool or exclude single-date queries. It provides the scope (a year) and notes the year-specific religious holiday limitation, which is useful, but lacks explicit alternative routing.

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