get_holiday

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds the detail that it wraps NBAPI GetHoliday, but says nothing about failure behavior when the key is unknown or the shape of the returned details. Adequate but thin beyond the annotation.

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?

A single front-loaded sentence identifying purpose, scope, and the underlying API call; nothing is wasted. It could arguably drop the NBAPI parenthetical, but that is minor.

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 read-only single-record lookup with a fully documented single parameter and annotation-covered safety, the description supplies enough to call the tool correctly. The only real gap is the absence of error/not-found behavior, which is a minor omission for this tool shape.

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?

With 100% schema coverage and only one parameter, the schema already states that HOLIDAYKEY is required and unique. The description restates its role (identifying the holiday) without adding format, case sensitivity, or example values, so baseline 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?

States a specific verb and resource ("Returns the details of a single holiday") and scopes it to one record via HOLIDAYKEY, which implicitly separates it from the sibling get_holidays plural listing. It stops short of naming the sibling explicitly, so differentiation relies on the word "single" rather than a direct contrast.

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 required key: an agent infers this is the tool to call when it already has a HOLIDAYKEY and wants one record. There is no explicit when-to-use/when-not statement and no pointer to get_holidays for enumerating holidays, so the routing guidance is only implicit.

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