due_date_calc

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

With no annotations, the description carries the full burden of behavioral disclosure. It does mention the cost of $0.001 USDC via x402, which is a useful constraint, but it completely omits what the tool actually does or what side effects occur, making this minimal transparency insufficient.

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 extremely short, but it is under-specified rather than concise. It provides no functional information and is structured as a title and a cost note, not a useful explanation.

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?

There is no output schema, no annotations, and no description of inputs or outputs. For a tool named 'due_date_calc', the description gives no clue about what problem it solves or what data it needs, making it completely inadequate for an agent to use correctly.

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 input schema exposes only a generic 'params' object with no specific fields, and the description adds no meaning about what parameters should be provided. The 100% schema coverage applies only to the wrapper object, not to actual parameter definitions, so the description fails to compensate.

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 'due date calc — Other Utilities tool' merely restates the tool name without stating what the tool does. It lacks a specific verb or resource, and does not distinguish itself from sibling tools like 'date_calc' or 'calculate_age'.

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?

No guidance is provided on when to use this tool or how it differs from alternatives. The description gives no context for selecting it over other date-related sibling tools.

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