date_calc

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions cost and category, revealing nothing about what the tool does, what inputs it expects, what it returns, or any side effects.

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 very short, but brevity here is under-specification rather than conciseness. While the first clause is clear about cost, the rest is purely categorical and adds no functional value.

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?

With no output schema and a generic input schema, the description must compensate, but it offers almost no context. For a likely multi-purpose date calculation tool, this is severely incomplete.

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?

The schema only has a generic 'params' object with no concrete parameters or field descriptions. The description adds no detail about what parameters date_calc accepts, making it impossible for an agent to construct a valid invocation.

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 merely restates the tool name 'date calc' and categorizes it as 'Other Utilities tool', with no verb or resource clarifying what it does. It does not distinguish this from the many other date-related tools like calculate_age or due_date_calc.

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?

There is no guidance on when to use this tool or when to prefer a sibling tool. The only practical detail is the cost, which says nothing about use cases or alternatives.

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