holiday_list

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's 'List' operation is consistent. The description adds the year-scoping constraint, but it does not disclose the return format, ordering, or behavior for invalid years. It adds minimal context 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 a single concise sentence that front-loads the verb and core purpose. Every word contributes to clarity, and there is no filler or 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 tool with one required parameter and no output schema, the description adequately conveys what the tool does. It could specify the return contents (e.g., holiday names and dates) or mention that it returns only national holidays, but the description is sufficient for a straightforward list operation.

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% for the single parameter 'year' with a description of 'Four-digit year.' The tool description merely reiterates that holidays are listed 'for a given year' without adding new semantic details about the parameter format, range, or examples.

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 'List all Japanese public holidays for a given year' uses a specific verb ('List') and resource ('Japanese public holidays') with a clear scope ('for a given year'), which distinguishes it from sibling tools like holiday_is_holiday (checks a specific date) and holiday_add_business_days (calculates date offsets).

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 implies that this tool is for retrieving all holidays for a year but does not explicitly state when to use it over alternatives such as holiday_is_holiday or holiday_business_days_between. No exclusions are mentioned, but the usage context is clear from the wording.

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