uae_holidays

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

With no annotations, the description fully discloses key behavioral traits: lunar holidays are marked 'provisional: true' until officially announced ~10 days before, and entries may include an optional 'note' with observance details. This provides critical context for interpreting results.

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 in the first paragraph for purpose, and two sentences in the second for behavioral details. Every sentence adds value with no 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?

For a simple one-parameter tool with an output schema, the description is complete. It covers purpose, parameter behavior (provisional status), and optional notes. The absence of explanation about return values is acceptable because the output schema exists.

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 input schema has 100% coverage, describing the single 'year' parameter well (default, type, and available years). The description does not add further semantics beyond what the schema already provides, so a baseline score 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 tool lists all UAE federal public holidays for a Gregorian year, with a specific verb ('list'), resource ('holidays'), and scope ('for a year'). It implicitly distinguishes from sibling tools like 'is_uae_holiday' and 'uae_next_holiday' by focusing on the full annual list.

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 effectively communicates the tool's purpose: to get a complete list for a year. While it doesn't explicitly contrast with sibling tools, the context from sibling names (e.g., 'is_uae_holiday', 'uae_next_holiday') and the clear scope make the use case obvious. A minor improvement would be to explicitly state when not to use it.

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