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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely useful context beyond them: the authoritative source (BLS schedule page), the fact it returns dates only and not payroll figures, the cap of 12 following dates, and a 1-credit cost. It does not describe caching/freshness of the schedule, which would be the remaining valuable detail.

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 question-first framing front-loads the purpose, then packs return shape, source, exclusions, and cost into a few dense clauses with no filler. The parenthetical cost note and the trailing disclaimer are compact, though the description is slightly cluttered by stacking multiple asides in one paragraph.

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, the description fully compensates by enumerating the returned fields (release date/time in three zones, reference month, up to 12 upcoming dates) and the data source. For a zero-required-parameter lookup tool, nothing an agent needs to call it correctly is missing.

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% and the single timezone parameter is fully documented with IANA examples and the Europe/London default, so the schema carries the load. The description adds marginal meaning by clarifying that the timezone controls the 'local time fields' and that results also include US Eastern and UTC regardless, but that is close to restating the schema.

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 leads with a specific question naming the exact resource (US Employment Situation: nonfarm payrolls and unemployment rate) and states the concrete return (next release date/time plus up to 12 following dates). It is clearly distinguishable from siblings such as next_jolts_release, next_cpi_release, and bea_release_dates_for_year because it names the underlying BLS report and explicitly excludes ADP payrolls and weekly jobless claims.

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 strong when-to-use context plus explicit exclusions (ADP private payrolls, Department of Labor weekly claims), which steers an agent away from misusing it. It stops short of naming the alternative tool an agent should call instead for ADP or claims data, so it is not a full when/when-not/alternative triad.

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