next_cron_occurrences

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

With no annotations, description provides key behavioral info: pure calculation, no side effects, up to 60 timestamps. But lacks details on error handling (invalid expression, timezone) and what happens if no future occurrences exist. Adequate but not comprehensive.

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, no fluff. Front-loaded with the core functionality. Every word contributes to understanding.

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?

Covers necessary aspects for a simple computation tool: purpose, input, output scope. Could mention error behavior or timezone but not critical. Given no output schema or annotations, it's reasonably complete.

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 coverage is 100%, so the description adds little beyond the schema. It reinforces that 'start' is after which occurrences are computed and that expression is five-field. Baseline 3 is appropriate.

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?

Clear verb ('computes') and resource ('five-field cron expression') specified. Distinguishes from siblings by emphasizing it's a pure calculation with no side effects. The description explicitly mentions the action, input, and output format.

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?

Implicitly states when to use via 'no job is created, stored, or executed' but doesn't explicitly list alternatives or when not to use. However, the context of sibling tools like 'validate_cron_expression' is clear, so a slight deduction.

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