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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is low, but the description adds no behavioral context at all — no indication of data freshness, granularity, or what the 'overview' and 'season comparison' actually contain. It neither contradicts nor enriches the annotations.

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?

One sentence, front-loaded with the core purpose. The trailing parenthetical is low-value filler that could be dropped without loss.

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 single-parameter read tool with no output schema, the description is adequate but thin: it never characterizes the returned 'overview' (time window, resort breakdown, units), which an agent would need to decide between this and get_state_snow.

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 parameter is documented with an example ('Region slug, e.g. colorado'), so the schema does the heavy lifting. The description only echoes 'for a region slug' and adds the public-site context, which is marginally useful but not new syntax or constraint info.

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 names a concrete resource (regional snowfall) and adds scope beyond the title with 'season comparison for a region slug'. It is clear what the tool returns, but it never differentiates itself from close siblings like get_state_snow or get_resort_snow, leaving the region-vs-state boundary to inference.

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?

There is no when-to-use guidance, no exclusions, and no named alternative, despite four other snowfall tools in the sibling list. The parenthetical about the 'same market dashboard as the public site' is a scope remark, not a routing rule.

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