uk_bank_holidays

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

No annotations, so description carries the burden. 'Source: gov.uk (keyless)' usefully discloses no auth needed, which is real behavioral value. However it does not state whether results are cached, refreshed, rate-limited, or whether 'upcoming' spans all future holidays or a limited window.

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 purpose, plus a source/auth note. No waste.

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 single-param read tool this is nearly adequate, but 'upcoming' is underspecified and the omission default is unaddressed. With no annotations or output schema, a bit more disclosure would help.

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 0% and the single param is an enum whose allowed values (england-and-wales, scotland, northern-ireland) are visible in the schema itself. Description does not explain the default when omitted (0 required params). Baseline for a single enum param is met but no added 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 (List) and resource (upcoming UK bank holidays) with scope (for a division). Clearly distinct from postcode-lookup siblings.

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?

Implied that it's for retrieving bank holidays, but no when-to-use/when-not guidance or alternatives named. No context on recency scope ('upcoming' is vague about lookahead window).

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