Next Holidays

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

No annotations are provided, so the description carries the behavioral burden. It does communicate a read-only lookup and a regional restriction, but it leaves unspecified details such as whether today is inclusive, the timezone used, and how unsupported countries are handled.

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 no filler. It front-loads the action and resource while including the key temporal and regional constraints.

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?

The tool is simple and has an output schema, so return-value documentation is not the description's responsibility. Still, the missing country value format and lack of explicit sibling differentiation leave meaningful gaps for an agent deciding how to invoke it correctly.

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 0%, and the only parameter 'country' is a bare string. The description adds the useful constraint that the country must be Latin American, but it does not specify whether the value should be a country name, ISO code, or other format, leaving the agent to guess.

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 the upcoming public holidays' for a Latin American country from today. The phrase 'from today' helps distinguish it from the sibling public_holidays, which likely returns a broader holiday set.

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 implies the tool is for upcoming holidays starting today, which gives some usage context. However, it does not explicitly name alternatives like public_holidays, long_weekends, or business_days, nor does it state 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.