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

With no annotations, the description carries the full burden, and it does disclose the hard cap of 5 results and the 'from today' anchor, which is real behavioral information. It omits the return shape (field names, whether state/region appears on each holiday), timezone handling, and what happens near year boundaries or when fewer than 5 remain.

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 short fragments, front-loaded with the scope constraint and containing no filler or redundancy. The 'FREE' marker is a single token that plausibly helps an agent weigh calling it.

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 zero-parameter, no-output-schema tool this covers the essentials, but it leaves a material ambiguity against sibling by_state: whether the returned holidays are national, per-state, or all-jurisdiction. That gap matters for correct tool selection more than the missing return-format detail.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The fixed 'next 5 from today' framing correctly signals that no filtering input exists.

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 concrete resource and scope: the next 5 Australian public holidays starting from today. The verb-less phrasing is still unambiguous because both the count and the time anchor are explicit. It loses a point because it never distinguishes itself from the sibling by_state, leaving ambiguous whether results are national-only or state-specific.

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 when-to-use or when-not-to-use guidance, and no reference to the alternatives by_state or is_holiday. 'FREE' hints at cost, not at selection criteria, so the agent must infer that this is the zero-argument 'give me something quick' option.

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