Indian central government holidays

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

Beyond the annotations, it discloses the authoritative source (DoPT order), supported years (2026 and 2027), coverage limits (no state, bank, or stock-exchange holidays), and a key accuracy caveat that moon-dependent festival dates may shift by a day.

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?

Two tightly written sentences, front-loaded with purpose and followed by exclusions and caveats. Every clause earns its place.

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?

For a simple two-parameter read-only lookup with no output schema, the description gives enough context to call it correctly, understand its coverage, and interpret its limitations. Nothing material 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?

Schema description coverage is 100%, so baseline is 3, but the description adds meaningful semantics: `date` triggers a check rather than a list, and when both parameters are given, `date` takes precedence. It does not add format details beyond what the schema already states.

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 states a specific verb and resource: it lists Central Government closed (gazetted) holidays for a year or checks whether a given date is one. It clearly scopes the dataset to DoPT orders and 2026-2027, and distinguishes this from broader holiday categories.

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 explicitly explains the two usage modes: list by year or check a date, and states precedence when both are supplied (`date` is used). It also names what is excluded, which prevents misuse for state, bank, or stock-exchange holidays.

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