Business Days

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

With no annotations, the description carries the full burden and does so well: it discloses weekend/holiday exclusion, ISO date format, inclusive endpoints, and the exact returned shape (count plus only the weekday national holidays that reduced the count). This gives an agent a realistic model of tool behavior.

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 purpose is front-loaded, and each subsequent sentence adds one distinct, needed fact: exclusions, format/inclusivity, return payload, and use cases. No filler or repetition; it is compact for the amount of behavior conveyed.

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 an output schema exists and no annotations, the behavior and return semantics are largely covered. The main completeness gap is the ambiguous country parameter, which is required and has no enum/format guidance; otherwise the description is sufficient to choose this tool over sibling holiday-listing tools.

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 coverage is 0%, so the description must document all parameters. It usefully specifies start_date/end_date as ISO and inclusive, but the required country parameter is only described as 'a Latin American country' with no accepted code format, country names, or supported-country list. An agent cannot reliably know what value to pass.

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 precise verb and resource: counts business days between two dates for Latin American countries, clarifying that weekends and nationwide public holidays are excluded. The focus on a computed count plus holiday details distinguishes it from listing siblings like public_holidays, next_holidays, and long_weekends.

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?

Names concrete use cases (SLA, payroll, logistics, settlement-date math) and defines the date-range semantics, which makes the intended context clear. It does not explicitly say 'use X instead for holiday lists' or list exclusions, but the use cases imply when this count tool is useful relative to siblings.

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