calculate_days_between

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

No annotations provided, so description carries the behavioral burden. It transparently states the tool is a calculation returning a structured object with weeks, months_approx, and working_days. No side effects are mentioned, which is appropriate for a pure calculation tool.

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?

Two sentences, no fluff. First sentence expresses purpose and output, second sentence offers related tools. Every word earns its place.

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 simple nature of the tool, complete schema coverage, and presence of an output schema (implied), the description sufficiently covers what an agent needs to know. No gaps identified.

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 provides full parameter descriptions (YYYY-MM-DD format). The description only adds that the tool calculates 'between two dates', which is already implied. With 100% schema coverage, baseline 3 is warranted; no additional semantic value beyond schema.

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 calculates days, weeks, approximate months, and working days between two dates. The verb 'calculate' and resource 'days between' are specific, and the output format is mentioned, distinguishing it from other date-related calculators.

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 mentions 'see list_bundles for related temps-rh calculators' but does not explicitly state when to use this tool over alternatives like 'calculate_age' or 'calculate_due_date'. The usage context is implied but not clearly delineated.

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