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

With no annotations, the description carries the full disclosure burden. It implies a pure, stateless computation and discloses that next run times are returned in an arbitrary UTC offset, which is genuinely useful behavior context, but it says nothing about invalid-expression handling, cost, or whether the result is deterministic across offsets.

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 filler, with the capability statement front-loaded and the usage hint appended. Every clause adds information.

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?

An output schema exists, so return-value explanation is unnecessary, and the expression syntax is well covered. However, with 0% schema description coverage on three parameters, the undefined `count` and the absence of any error/validation behavior leave the definition short of complete for an agent invoking it blind.

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 0%, so the description must compensate. It does add meaning for `expression` (accepted formats) and maps 'any UTC offset' to `timezone_offset_hours`, but the `count` parameter — which controls how many upcoming runs are listed — is never mentioned or bounded, leaving a real gap.

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?

States a specific verb+resource ('Explain a cron expression') and immediately bounds the accepted syntax (5 fields, names like mon-fri, @daily) and the output (plain English + next run times). No sibling tool overlaps with cron parsing, so it is unambiguous without naming an alternative.

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 closing clause 'Use to check schedules before deploying jobs' gives explicit usage context, which is more than most tools provide. It stops short of stating exclusions or alternatives (e.g., use time_zone_convert for offset math), so it is a clear context without routing guidance.

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