japan_holidays

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does add context that the data comes from the official Cabinet Office syukujitsu.csv and is bundled, implying deterministic local data. However, it does not disclose error behavior, valid year ranges, or other edge cases, leaving gaps for an agent to discover at runtime.

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 one concise, front-loaded sentence. It starts with the verb 'List' and immediately states the resource and scope, with a parenthetical for source context. No wasted words.

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?

The tool is simple (1 param) and has an output schema, so the description need not detail return values. The description provides essential purpose and data source, but it lacks guidance on when to use this over the sibling 'is_japan_holiday', making the overall context incomplete for an agent deciding between tools.

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 single parameter 'year' in the schema is just an integer. The description clarifies that this is the year for which holidays are listed, adding meaningful semantic context. For a single simple parameter, this is sufficient even though schema description coverage is 0%.

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 Japanese national holidays for a year' clearly states the tool's function with a specific verb and resource. However, it does not explicitly distinguish itself from sibling tool 'is_japan_holiday' (which likely checks a single date), so it is clear but lacks explicit sibling differentiation.

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?

No guidance is provided on when to use this tool versus alternatives like 'is_japan_holiday'. The description only states what it does, with no mention of use cases, exclusions, or alternative tools.

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