get_holidays

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses the read-only nature and the maximum 2-year window, which are real operational constraints. However, it says nothing about auth requirements, rate limits, pagination, or how results are aggregated/deduplicated across multiple countries, leaving meaningful gaps for a multi-country query tool.

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?

Three short sentences, front-loaded with the core action and scope, then a usage cue, then the safety trait. No redundancy or filler; every sentence carries information.

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 4-parameter tool with no output schema and no annotations, the description covers purpose, range limit, and read-only status but stops short of clarifying the return shape (e.g., grouped per country, holiday type fields) or permission needs. Adequate but with clear omissions.

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%, so the schema already documents format (YYYY-MM-DD, UTC), ISO codes, the max-5 limit, and the days_off_only default; baseline is 3. The description adds only the 2-year range cap and the observance-vs-day-off concept, which is marginal value beyond the schema.

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?

Names a specific verb (Get) and resource (public holidays and memorial days) with explicit scope: one or more countries within a bounded date range. This is clearly distinguishable from siblings like get_events or list_calendars, which return user calendar items rather than national holidays.

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 sentence 'Useful for scheduling around days off' hints at the intended use case but never states when to choose this tool over get_events or how the two relate. No exclusions, prerequisites, or alternative-routing guidance are given, so usage is only implied.

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