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

With no annotations, the description usefully discloses that the tool is deterministic and not LLM-based, and it explains the x402 payment requirement, price, and HTTP endpoint. However, it does not state batch behavior, side effects, rate limits, or what happens if payment is missing.

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 compact and front-loads the capability list, with payment and transport details following. It is somewhat dense and includes minor framing like 'for AI agents', but there is little wasted text.

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 paid, batch-oriented date tool with no annotations, no output schema, and 0% schema coverage, the description is missing critical operational detail: batch semantics, op values, parameter mapping, request/response shape, and sibling differentiation.

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 explain the three parameters. It only says 'GET query params or POST JSON' and references params._meta for payment; it never explains what op, from, and to mean or which op values map to the listed capabilities.

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 names a broad domain—deadline and date arithmetic—and lists capabilities like business days, date differences, timezone conversion, recurring schedules, and risk scoring. But it never explains what the batch-specific tool does, and it does not distinguish due__batch from the sibling due__due or other date tools.

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?

It gives no when-to-use or when-not-to-use guidance, no comparison with due__due or bizcal_api__batch, and no indication of which operations are batched versus single. The GET/POST and payment notes describe transport, not selection criteria.

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