add_business_days

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

No annotations are provided, so the description carries the full burden. It discloses key behavior (skipping weekends and US federal holidays) and supports negative numbers for subtraction. However, it does not mention edge cases like start_date falling on a weekend/holiday, date format expectations, or output details.

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 a single concise sentence that front-loads the core action and constraints. Every phrase adds value ('skip weekends and US federal holidays', 'negative number') without waste.

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 but still lacks details about input date format, behavior when start_date is a non-business day, and output schema specifics. With no annotations and minimal parameter guidance, the description is adequate but not complete for a production tool.

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 schema provides only types (string, integer) with 0% coverage from the description. The description only hints that 'days' can be negative but does not clarify the expected date format (e.g., YYYY-MM-DD) or the semantics of 'days' beyond business-day count. This is insufficient compensation for the lack of schema 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 uses a specific verb ('Add') with a clear resource ('business days to a date') and specifies scope ('skipping weekends and US federal holidays'). It clearly distinguishes itself from siblings like business_days_between and federal_holidays.

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 states the operation (add/subtract business days) but does not explicitly mention when to prefer this over alternatives. The existence of sibling tools like business_days_between suggests different use cases, but no direct comparison or exclusion is given.

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