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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds a genuinely useful data-freshness caveat that annotations cannot express: lift and run counts are reported status, not guaranteed live. It omits error behavior for unknown resorts and any caching/latency notes.

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 tight sentences with zero filler; the payload of what is returned comes first and the caveat is appended after. Nothing redundant or padded.

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 usefully enumerates the return contents (snow, lift/run counts, weather, season state), which covers the most important gap. For a read-only, one-parameter tool the remaining omissions, resort identifier format and unknown-resort behavior, are minor.

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 0% for the single required 'resort' parameter, so the description must carry the load. It never clarifies whether 'resort' is a name, slug, or ID (only maxLength 100 in schema). The name is largely self-explanatory and the surrounding context scopes the entity, so this is a mild but 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 ('Get') and enumerates the returned resources (current snow, lift and run counts, weather, season state), which is far more than a restatement of the title. It does not, however, name or contrast itself with close siblings such as get_forecast, get_snow_reports, or get_extended_outlook, so an agent must infer the boundary itself.

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 word 'current' implicitly signals this is the now-snapshot tool versus the forecast/outlook siblings, but the description never states when to choose it over get_forecast, get_snow_reports, or get_extended_outlook, and lists no exclusions. Usage is implied rather than stated.

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