calculate_days_between

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

No annotations provided, so the description must convey behavior. It discloses the return structure ({weeks, months_approx, working_days}) but does not mention date ordering, inclusive/exclusive endpoints, or error handling for invalid dates. Some behavioral traits are implied but not explicit.

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, zero wasted words. First sentence states the core function; second adds return type and a cross-reference. Highly efficient for its purpose.

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 date calculator with an output schema (implied), the description is adequate. It covers key return fields and points to related bundles. Minor gaps: no mention of date order validation or handling of non-date inputs, but these are common to similar tools.

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?

Input schema has 100% coverage with descriptions for both parameters (format YYYY-MM-DD). The description does not add semantic value beyond the schema, so baseline 3 applies. It does not explain what 'start_date' and 'end_date' represent or any constraints.

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 'Calculate' and the resources 'days, weeks, approximate months and working days between two dates', distinguishing it from the many sibling calculators with similar but distinct purposes.

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 briefly mentions 'See list_bundles for related 'temps-rh' calculators', hinting at alternatives but providing no explicit when-to-use or when-not-to-use guidance. It lacks context for choosing this tool over siblings like 'calculate_working_days' or 'calculate_time_difference'.

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