Thai Public Holidays

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is known to be safe. The description adds behavioral context: it returns a disclaimer, mentions lunar holidays are fixed by annual announcement, and advises verification for critical deadlines, which is valuable beyond the annotations.

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 well-structured with purpose, args, returns, and usage notes. It is front-loaded and every sentence adds value. It could be slightly more concise in the returns section, but overall it's effective and not verbose.

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 tool's simplicity (one parameter, no output schema), the description is thorough. It explains the output format with all fields, includes a disclaimer, and provides usage guidance and caveats. This fully compensates for the lack of output schema.

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% description coverage, so the parameter is already documented. The description restates 'one of 2025, 2026' but adds no new semantic detail beyond the schema. A baseline score of 3 is appropriate since the description doesn't compensate further.

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 'List Thai public holidays for a given year (2025, 2026), with dates, Thai/English names, and a flag for lunar-calendar holidays.' This provides a specific verb and resource, and distinguishes from sibling tools like thai_address_normalize or thai_company_lookup which serve different purposes.

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 explicitly suggests use cases: 'Use when scheduling anything in Thailand: payment due dates, meeting planning, delivery estimates, contract deadlines.' It also notes caveats about lunar holidays and bank holidays. While it doesn't list alternatives, the sibling tools are unrelated, so no explicit 'when not to use' is necessary.

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