add_business_days

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

Given no annotations, the description fully reveals behavior: it handles negative values, adjusts weekends per country (e.g., Friday/Saturday in Saudi Arabia), skips only real public holidays not observances, and returns result date, weekday, and skipped weekends/holidays.

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 two sentences, front-loaded with 'USE THIS', and contains no redundant information. Every clause adds meaningful context.

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?

With no output schema and four parameters, the description covers all essential aspects: purpose, input parameters, behavior (weekends, holidays, negative days), and output. It is fully adequate for an agent to select and invoke the tool 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 coverage is 100%, so baseline is 3. The description adds value by explaining country-specific weekend behavior and the distinction between public holidays and observances, which goes beyond the schema's parameter 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 explicitly states the tool computes deadlines or settlement dates by adding/subtracting business days, using a clear verb and resource. It distinguishes itself from siblings like count_business_days and is_business_day by focusing on date calculation rather than counting or checking.

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 begins with 'USE THIS' to strongly indicate when to use, and provides context about computing deadlines instead of manual counting. However, it does not explicitly state when not to use or mention alternatives.

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