Check whether a given date is a public holiday in a country (identified by its ISO 3166-1 alpha-2 code), and return the holiday name if so. Backed by an authoritative public-holiday dataset.
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Date "YYYY-MM-DD". | |
| country_code | Yes | ISO country code, e.g. "US", "ES", "IN". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It states the tool checks for holidays and returns the name, and mentions the authoritative dataset. However, it omits the return format (e.g., raw boolean or object), error handling for invalid inputs, and any side effects. With no annotations, more detail would be beneficial.
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 extremely concise: two sentences front-loading the core functionality and a brief note on data source. No superfluous information. Every sentence adds 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?
Given the simple nature of the tool (2 params, no output schema, no annotations), the description adequately covers the what and why, but lacks specifics on the return structure (e.g., what is returned when not a holiday) and error messages. For a minimal tool, it is mostly complete but has some gaps.
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?
Both parameters are documented in the schema with descriptions for date format and country code (ISO alpha-2). The description reiterates this but adds no new parameter semantics beyond what schema provides. The mention of an authoritative dataset is contextual but not parameter-specific. Schema coverage is 100%, so a baseline of 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?
The description clearly states the verb 'check' and the resource 'whether a date is a public holiday in a country'. It distinguishes from sibling tools like convert_timezone and date_math, which are about time/date conversion and math, not holidays. The purpose is 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 does not provide explicit guidance on when to use this tool versus alternatives like convert_timezone or date_math. While the tool's purpose is clear, an agent might benefit from context about when to choose this tool over other date-related tools. No 'when not to use' or comparisons are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: conversion (single and batch), arithmetic, meeting scheduling, holiday checking, timezone lookup, current time, and offset. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., convert_batch, list_timezones, is_holiday). Minor variations like 'now_in' and 'tz_offset' still adhere to the pattern.
Nine tools is ideal for a timezone toolkit. Each tool serves a distinct and necessary function without being excessive or insufficient for the domain's scope.
The toolset covers all major timezone operations: conversion, arithmetic, current time, offset, discovery, holidays, and meeting slot calculation. No obvious gaps for common use cases.