calculate_date

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

No annotations are provided, so the description carries the burden. It lists parameters and defaults but does not disclose potential side effects, error handling, output format, or constraints (e.g., date format, timezone handling). The output schema exists but is not referenced.

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 concise: a brief purpose sentence, a usage sentence, and a parameter list. No fluff. The structure is front-loaded with purpose. Minor improvement could be bullet points for parameters.

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 tool has 6 parameters (0 required) and an output schema, the description covers the main operations and parameters but lacks details on edge cases, default behavior per op, and validation. It is adequate for a calculator tool but leaves some gaps for an AI agent.

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%, so the description must compensate. It provides a clear parameter list with brief explanations for each (op, date1, date2, days, months, years), which adds meaning beyond the schema's just names and defaults.

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 performs date arithmetic and difference calculations, and lists specific use cases (find days between dates, add/subtract time, get date info). This distinguishes it from sibling date tools like calculate_age or calculate_business_days.

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 explicitly says when to use the tool (for finding days between dates, adding/subtracting time, getting date info). However, it does not provide exclusions or comparisons to alternative sibling tools.

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