business_days_between

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

No annotations are provided, so the description must carry the full burden. It explains the half-open nature and negative result behavior. However, it does not disclose the source of public holidays, potential rate limits, or whether the tool requires network access. These gaps lower transparency.

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 the core purpose, and contains no redundant words. All information is pertinent and efficiently 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 the 4 parameters, no annotations, and no output schema, the description is quite complete. It covers the core functionality, half-open interval, and negative results. A minor gap is the lack of mention of the holiday calendar source (e.g., defaults to US), but overall very good.

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?

With 100% schema description coverage, the baseline is 3. The description adds context about half-open interval and negative results, which relates to start_date and end_date, but does not add new information about country or subdivision beyond the schema. Value added is marginal.

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 counts working days between two dates, excluding weekends and public holidays. It also explains the half-open interval, distinguishing it from siblings like is_business_day or next_business_day.

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 provides basic usage context (half-open interval, negative results) but does not explicitly guide when to use this tool over siblings such as add_business_days or is_business_day. No exclusion criteria are mentioned.

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