get_public_holidays

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

No annotations are provided, so the description carries full burden. It fails to disclose any behavioral traits such as data freshness, rate limits, authentication requirements, or output structure. The description only covers purpose and parameters, leaving significant gaps.

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 concise with no unnecessary text. It uses a clear two-sentence introduction followed by parameter details, making it easy to scan. Every sentence serves a purpose.

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?

Given the moderate complexity and the presence of an output schema (not shown), the description is mostly complete. It covers country support, default values, and usage. However, it lacks information about the output format or error handling, which would improve completeness.

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 description adds substantial meaning beyond the schema (which has 0% coverage). It explains that 'country' is a two-letter code with default 'GB' and supported values 'GB', 'US', 'IE'. For 'year', it states default as current year (though schema lists 2026, a minor discrepancy) and gives an example. This compensates well for the schema's lack of descriptions.

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 clearly states 'Get public holidays by country and year' with a specific verb and resource. It includes usage scenarios like checking bank holidays and planning. The tool is distinct from all listed siblings, which are unrelated.

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?

Explicit usage contexts are provided (e.g., 'check bank holidays, plan around public holidays, or calculate working days'). However, no exclusions or alternatives are mentioned, and the description does not specify when not to use this tool.

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