uae_next_holiday

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses that an earlier unannounced lunar-date candidate is returned separately as `next_provisional_candidate` and is deliberately not treated as confirmed, which the agent could not learn from annotations alone.

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 short sentences, front-loaded with the core action and followed by the one caveat that matters. Nothing is padded.

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?

An output schema exists, so return formatting need not be explained, and the description covers the one subtlety an agent must know (confirmed vs provisional). Complete for a single-optional-parameter read tool, with only the sibling routing left implicit.

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% and the single parameter already documents 'ISO date YYYY-MM-DD. Defaults to today.' The description adds only the notion of a 'reference date' that the search starts from, which is a marginal restatement rather than new semantics.

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?

States a specific verb and resource ('Find the next confirmed UAE public holiday') plus the scoping condition ('on or after a reference date'). The word 'next' plus 'confirmed' implicitly distinguishes it from the broader uae_holidays and the boolean is_uae_holiday without ambiguity.

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?

Usage is implied by the phrase 'on or after a reference date,' and the second sentence clarifies what the tool does and does not present as a day off. However, it never explicitly names when to prefer this over uae_holidays or is_uae_holiday, leaving the agent to infer the routing.

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