get_colombia_holidays

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

Annotations already declare readOnlyHint and idempotentHint, so safety is clear. The description adds valuable behavioral details: the 'Ley de Puentes' rule that most holidays move to Monday, dynamic calculation of Easter-dependent holidays, and that it returns exactly 18 holidays. No contradictions.

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 4 sentences, each adding value. It front-loads the purpose and then provides context on law, output structure, and use cases. No wasted words.

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 an output schema, the description does not need to explain return values. It adequately covers usage, legal context, count, and output structure, making it fully informative for an agent.

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 only parameter is 'year' with full schema description. The description does not add additional meaning beyond the schema, but the schema is already clear and covers 100%. Baseline 3 is appropriate.

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 Colombian national public holidays for a given year as a structured list with specific fields (date, name, name_en). It distinguishes itself from sibling tools by specifying Colombia, and the sibling list includes other country holidays, making the purpose unique.

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 explicitly advises when to use this tool: for calculating Colombian business deadlines, factura electrónica payment dates, or scheduling tasks. It does not state when not to use or explicitly name alternatives, but the sibling tools for other countries imply those are alternatives.

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