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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered structurally. The description adds real context: the data comes from the nearest long-record station and includes record years, which hints at the underlying data source and vintage. It does not say what happens when no long-record station exists or how 'today' is timezone-resolved.

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?

A single well-formed sentence that front-loads the comparison and then enumerates the payload (averages, records, record years). No filler, no repetition of the title. Slightly dense for one sentence, but nothing is wasted.

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?

There is no output schema, so the description carries more burden, and it does partially discharge that by naming the returned elements. It still omits units, the station identity in the response, and date/timezone basis for 'today'. Adequate but with visible gaps for a no-output-schema tool.

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 100%, so lat, lon, and city are already documented, including the city-vs-lat/lon rule. The description adds only indirect meaning ('nearest long-record station' explains why precise coordinates matter) and no format or unit guidance. Baseline 3 applies when the schema does the heavy lifting.

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 states a concrete subject: how today compares to the historical record for this calendar date, including averages, records, and record years, at the nearest long-record station. That is specific enough to separate it from forecast and why_this_forecast. It stops short of explicitly contrasting with whats_unusual, which is the closest sibling.

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 comparison framing implies the use case (checking where today sits against climatology) but there is no explicit when-to-use, when-not, or named alternative. An agent inferring 'historical comparison vs. current forecast' can route correctly, but must do so from implication rather than instruction.

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