business_days_between

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

No annotations provided, so the description carries full burden. It details behavior: only weekday holidays listed, inclusive/exclusive effect, 100-year span limit, and error conditions (ValueError for invalid input). This is comprehensive.

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?

Well-structured with paragraphs and bullet points (Args, Returns, Raises). Every sentence adds value, though slightly verbose. Could be tightened but overall effective.

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 5 parameters, output schema existence, and sibling tools, the description is complete. Explains return dict structure, error types, and distinguishes from siblings like get_supported_countries.

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 description coverage is 0%, but the description fully compensates. It explains each parameter: date format, country case-insensitivity, inclusive default, subdiv case-sensitivity and relation to get_supported_countries. No ambiguity remains.

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's purpose: 'Count business days and list weekday holidays between two dates.' It distinguishes itself from sibling tools like is_business_day and list_holidays by combining counting and listing.

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?

Provides explicit use cases: 'measure working-day spans for SLAs, delivery windows, or payroll periods.' It explains what holidays are included/excluded but does not mention when to avoid this tool or suggest alternatives like is_business_day for single date checks.

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