get_spain_holidays

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

Annotations already declare readOnlyHint and idempotentHint. The description adds behavioral details: 9 mandatory national holidays, output structure with date and names, and the exclusion of regional holidays. No contradictions with annotations.

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 sentences pack all necessary information: what it does, output structure, and limitations. No redundant words, directly to the point.

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 presence of annotations, full schema coverage, and an output schema, the description is complete enough. It clarifies the return format and the scope (national only), which is valuable for an agent comparing with sibling tools like get_france_holidays or get_public_holidays_range.

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 single parameter 'year' is fully described in the schema (100% coverage). The description adds no new parameter meaning beyond the schema, but reinforces that the year is used to filter holidays, which is expected. 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?

The description clearly states the tool returns 'all Spanish national public holidays for a given year' as a structured list with specific fields. It distinguishes itself from sibling tools targeting other countries (e.g., get_france_holidays) and explicitly excludes regional holidays, providing precise scope.

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 description indicates when to use the tool (to obtain Spanish national public holidays) and when not (for regional holidays). It implicitly suggests alternatives like regional-specific tools, but does not explicitly name sibling tools for regional holidays.

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