holidays_by_country

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no mention of what the result contains (holiday names, dates, types), whether it errors on unsupported country codes, or whether missing/unrecognized years fall back to the default.

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 sentence with zero filler and the key object front-loaded. It is arguably too terse rather than bloated, but every word earns its place.

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 two-parameter read tool with rich annotations and a fully documented schema, the minimum viable information is present. However, with no output schema, the description should at least hint at the return shape (a list of holidays with dates) — that is left entirely unspecified, and the relationship to the other holidays_* tools is unaddressed.

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 description coverage is 100%: the schema documents country_code as a 2-letter ISO code with examples and year as defaulting to the current year. The description merely restates that both are inputs, adding no format hints or edge-case behavior beyond the schema. Baseline 3 applies.

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 ('Get public holidays') with the scoping dimensions (country and year), which is clearer than the bare name. It does not distinguish itself from close siblings such as holidays_next, holidays_countries, or holidays_long_weekends, so an agent cannot tell from the description alone which holiday tool to pick.

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?

There is no statement of when to use this tool versus holidays_next (upcoming holidays) or holidays_countries (list supported countries), both of which sit adjacent in the catalog. Usage is only implied by the description's noun phrase; the agent must infer selection criteria.

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