Calculate the exact difference between two ISO 8601 dates in days, business days, and hours. Provide two dates to get precise date intervals for planning and analysis.
Compute the exact difference between two dates in days, business days, and hours
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | First ISO 8601 date/datetime | |
| b | Yes | Second ISO 8601 date/datetime |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It states the computation but does not disclose output format, error handling, or whether timezones are considered. For a calculation tool, this is a moderate gap.
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, front-loaded sentence with zero waste. It states the purpose and the specific output units efficiently.
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?
For a simple tool with full schema coverage and no output schema, the description covers the core purpose but omits output format details (e.g., whether it returns an object with separate fields or a combined string) and edge cases like invalid input. This leaves minor but notable gaps.
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% with clear descriptions for both parameters ('First ISO 8601 date/datetime' and 'Second ISO 8601 date/datetime'). The description adds no extra semantic detail beyond restating that it takes two dates, so it meets the baseline for high schema coverage.
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 a specific verb 'Compute' and resource 'exact difference between two dates' with explicit units (days, business days, hours). It distinguishes itself from sibling tools like parse_date or date_add by focusing on difference calculation.
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 does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or conditions like timezone handling. However, the operation is self-evident for date comparison, so some guidance is implied but not articulated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.